Guideline for leveraging GitHub Actions cache
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 301
- Forks
- 43
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 20
Description
Hi,
I believe it would be super helpful to provide some guidelines on how to implement gha caching while using this action.
Docker's documentation also doesn't mention anything about when using bake:
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 project file or test is named. Start by reviewing the action's existing documentation and the linked Docker GitHub Actions cache page, then identify what bake users need to know. Done means the documentation gives clear guidance for implementing GHA caching with this action and bake.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100