Document how cache scoping works with tags
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
The documentation says that caches are scoped to branches. Suppose I am building from a tag? The tag might be at the tip of one or more branches, or it might not be at the tip of any branch. How does it decide which caches are in scope? This information should be in the documentation. See also #1178, #79, #1175
Thanks!
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
Read the current cache-scoping documentation and the related issues #1178, #79, and #1175. Confirm how caches are selected when a workflow builds from a tag, including tags at branch tips and tags not at any branch tip, then document those cases clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100