Live Update with only requires duplication
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Scenario:
I have a repo that has many files I don't want to cause a rebuild. So I want to use the only parameter to docker_build. I also want it to be fast, so I use live_update. The files don't all go to the exact same directory.
Question:
Do I have to list each file/directory twice (once in only, once in a sync line)? Is there fall-through? We should document this case (and consider improving the behavior).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the docker_build documentation for the only parameter and the live_update sync configuration, then verify whether paths fall through between them. Done means documenting whether files must be listed twice and clearly separating any behavior improvement from the documentation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100