feat: add cache-from/cache-to passthrough to build-push-action - #4
Open
ps-20x wants to merge 1 commit into
Open
Conversation
Lets consumers wire external build caches (e.g. GitHub Actions cache, registry cache) through to docker/build-push-action, which already supports cache-from/cache-to natively. Without this the composite action forces every build to start cold, since GitHub-hosted runners are fresh VMs per job and local buildx cache never persists across runs regardless of builder lifecycle. Backward compatible: both inputs default to empty string, matching existing optional-input behavior in this action.
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
1 participant
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.
Lets consumers wire external build caches (e.g. GitHub Actions cache, registry cache) through to docker/build-push-action, which already supports cache-from/cache-to natively. Without this the composite action forces every build to start cold, since GitHub-hosted runners are fresh VMs per job and local buildx cache never persists across runs regardless of builder lifecycle.
Backward compatible: both inputs default to empty string, matching existing optional-input behavior in this action.