Cache-hit returns true when there is a match with restore-keys as well
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
When using the restore action, we want to know if there is an exact match with key or if we have an older match. We see that the return value for cache-hit is also 'true' when there is only a match with one of the values in restore-keys
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 by tracing how the TypeScript action determines and exposes the cache-hit output, then reproduce a run with an exact key match and one with only a restore-key match. Add or update tests for both cases; done means cache-hit is true only for an exact key match and false for restore-only matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100