refactor: use new gitContext for build context resolution#1505
Merged
crazy-max merged 4 commits intodocker:masterfrom Apr 9, 2026
Merged
refactor: use new gitContext for build context resolution#1505crazy-max merged 4 commits intodocker:masterfrom
crazy-max merged 4 commits intodocker:masterfrom
Conversation
crazy-max
force-pushed
the
refactor-git-context
branch
2 times, most recently
from
7c4ce8b to
fed34ab
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
refactor-git-context
branch
from
fed34ab to
2d8f2a1
Compare
tonistiigi
approved these changes
Apr 9, 2026
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
2 participants
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.
See https://github.com/docker/build-push-action/actions/runs/23849597824/job/69525749466?pr=1505#step:6:190 as an example