alphagov / alphagov/data-community-tech-docs
Cache GitHub actions build steps
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 7
- Forks
- 4
- Avg merge
- 13h 45m
- Merged PRs (30d)
- 19
Description
Per reviewer comments of #74
Caching dependencies: We might want to cache our installed gems with actions/cache. This could speed up build times. I'm not sure how often we build or rebuild, so perhaps this doesn't matter. I assume we rebuild when a change is merged and a PR approved.
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
Review the repository's GitHub Actions workflow and the linked official caching documentation first. Add caching for the installed gems so repeated builds can reuse them, then verify that the workflow completes successfully and uses the cache on subsequent runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ruby
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100