Support some form of "read only cache" or "centralized cache"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
Description:
@actions/cache now ships @actions/cache/save and @actions/cache/restore actions to easily implement different caching strategies. One of the strategies they document is "Make cache read only / Reuse cache from centralized job", where you only restore in jobs.
Justification:
It'd be nice to support this caching strategy / others in the future in this action natively to allow users to easily adopt or test strategies without having to opt out of this action's caching and implementing them themself.
Are you willing to submit a PR?
If I can find time
Contributor guide
No contributing guide indexed for this repository
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 by reading the @actions/cache/save and @actions/cache/restore actions and the documented read-only or centralized-job strategy. Define the supported caching behavior for setup-node and determine how workflow users can verify that jobs restore caches without saving them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100