buildx(build): resolveWarnings from metadata#362
Merged
crazy-max merged 1 commit intodocker:mainfrom Jun 26, 2024
Merged
Conversation
crazy-max
force-pushed
the
buildx-build-resolvestatus
branch
2 times, most recently
from
63f6086 to
931a895
Compare
This was referenced Jun 14, 2024
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
buildx-build-resolvestatus
branch
from
931a895 to
630b180
Compare
crazy-max
changed the title
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.
alternative to and closes #302
needs docker/buildx#2551follow-up of docker/buildx#2551 so we can resolve warnings from the metadata file.