integrate with the tool cache somehow?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 392
- Forks
- 52
- Avg merge
- 52m
- Merged PRs (30d)
- 7
Description
Github Actions has an API for working with the tool cache:
https://github.com/actions/toolkit/tree/main/packages/tool-cache
This seems like a reasonable fit for this action. I don't know if just the installer download should be cached, or if the install should live in the tool cache, as the tool cache is preserved between runs, unlike the runner _temp directory where this stuff goes now.
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 GitHub Actions tool-cache API at the linked actions/toolkit package. Compare caching only the installer download with placing the installation in the tool cache, considering that the tool cache persists between runs while the runner _temp directory does not. Done means selecting and implementing a clear caching approach for this action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100