ci: warm BuildKit cache on trusted pull requests - #44
Draft
jelias2 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enable GitHub Actions BuildKit cache exports for same-repository pull requests. Fork PRs remain excluded.
Why
The reusable workflow already restores
type=ghacache for every build, but only protected branches exported new cache entries. Dependency-changing PRs could not warm their own cache, so later pushes repeated expensive container compilation.Change
is_fork_pr == falsein build and Bake modes.Validation
Rollout
Consumers pinned to this reusable workflow need a follow-up SHA bump after this merges. The paired
op-rbuilderPR documents that dependency.