Repository navigation
docs(bake): describe the per-target cache of the shared reusable - #205
Conversation
Since netresearch/.github#525 the build-container-bake reusable writes one GHA cache per target and, on the weekly rebuild, also clears a cache-from declared in the bake file. The comment no longer says that a cache declared here would still apply. Assisted-by: claude-code:claude-opus-5-5 Agent-Session: 4862b645-a608-44d1-a9a8-fe50bb3b2e23 Agent-Host: 0493f0 Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ⬇️ Low Change: Other Merge Risk: ⚪ Minimal · up to
|
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Automated approval for maintainer PR
All automated quality gates passed. See SECURITY_CONTROLS.md for compensating controls.



When this is merged, the comment on the
minimaltarget indocker-bake.hcldescribes the cache as the build-container-bake reusable handles it since netresearch/.github#525: one GHA cache per target, none read on the weekly rebuild. No build behaviour changes.The removed sentence said that a
cache-fromdeclared in the bake file would still apply on the weekly rebuild. Since netresearch/.github#525 the reusable clears it with an empty<target>.cache-from=.Assisted by claude-code:claude-opus-5-5 — Session 4862b645-a608-44d1-a9a8-fe50bb3b2e23