Create an option `restore-only`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
While reading the readme I noticed that lookup-only says it does a lookup but no download.
I would like to benefit from a cache entry if there is one, but not saving the result I would have made.
This would allow deployments to get the cache from the main branch but not overwrite it.
Same for pull requests.
Why not having restore-only ?
Related to https://github.com/actions/cache/issues/109 but for read only
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 README's description of lookup-only and review the related actions/cache issue 109 to understand the intended read-only behavior. Trace how cache restoration and saving are exposed to the action, then define restore-only so it can restore an existing cache without saving a new result; completion should include documentation and coverage for deployments and pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100