Save package cache as a post build step
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 392
- Forks
- 52
- Avg merge
- 52m
- Merged PRs (30d)
- 7
Description
This action is pretty neat, but one thing that would be nice is if saving the package cache could be deferred until after the build is done.
This would be ideal because I have a build script that installs many dependencies (and where it's not really practical to list them out directly in the workflows yml), so it would be nice if it cached those packages too. Not entirely sure if this is possible, although I see actions/cache does it as a post build step.
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 action's current package-cache handling and compare it with the post-build behavior of actions/cache. Check whether packages installed by a workflow build script can be captured after the build; done means those packages are restored on a later run without listing them individually in the workflow YAML.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100