`cache-saved` output for `cache/save`
Open
Nobody has claimed this yet.
stale
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
cache-hit exists for cache/restore and provides whether there was a cache hit. However, when using cache/save, there is no similar output which can be used to check for whether the cache was saved. This could be useful when building composite actions and checking whether the action was triggered? Feel free to close this issue if it isn't considered useful.
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
No file or test is named in the issue. Start by locating the cache/save entry point and comparing its outputs with cache/restore's cache-hit behavior; done means composite actions can check whether saving the cache succeeded or occurred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, 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