Support github cache
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 276
- Forks
- 37
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 12
Description
Dear @aminya,
Thank you for providing this action. It is really helpful to me.
I would like to ask if there is any technical reason why github cache cannot be leveraged somehow to avoid re-installing the same packages every time. My pipelines run the same env for multiple jobs and sometimes setup-cpp is the step that takes most of the time (example: https://github.com/DiamonDinoia/finufft/actions/runs/13046204138/job/36416878122). Is it possible to cache the installations, or the resulting image entirely to avoid doing the same work all the time?
Thanks,
Marco
edit: if you can help me setting up custom docker images. I am happy to contribute to the documentation
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 files or tests are named. Start by reviewing setup-cpp’s installation flow and GitHub Actions cache support, then determine whether package installations or resulting Docker images can be reused across jobs. Done means a supported caching or custom-image approach is documented and validated in a representative workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100