docker / docker/github-builder
Allow per target registry based cache
Open
Nobody has claimed this yet.
kind/enhancement
status/triage
- Dominant language
- No language data
- Stars
- 83
- Forks
- 23
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
Description
Allow the use of a per target registry based cache instead of the gha cache. (with zstd compression if possible)
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
Start by reviewing the reusable GitHub Actions workflows and the current gha cache configuration. Trace how build targets are defined and how cache settings are passed to them. Done means each target can use a registry-based cache instead of gha, with zstd compression if supported; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100