Check cache hit before uploading on Post Setup Node
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
Description:
Check for a cache hit before uploading.
On a large codebase with a lot of dependencies, the upload can take some time. If you have a lot of concurrent actions, they will all upload the same cache, even if a job that finished earler has already uploaded a cache for the hash.
Justification:
Would save a lot of time, network bandwidth, and trees!
Are you willing to submit a PR?
Yes - I can have go if you think this is feasible/worthwhile!
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 with the Post Setup Node cache-upload flow described in the issue and trace where cache hits are available before an upload begins. Done means concurrent jobs avoid uploading the same cache when an earlier job has already stored it; verify the behavior with the repository's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100