Remove Concurrency Checks from Validate Docker Build#1153
Merged
Conversation
They aren't needed as this never pushes to anywhere so who cares if we run this a bit too aggressively to maintain perfect resolution of if the build works.
|
|
GHCR image refs for this PR:
This comment is generated from PR metadata only. It does not checkout or run PR code and is generated in a static manner |
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.
They aren't needed as this never pushes to anywhere so who cares if we run this a bit too aggressively to maintain perfect resolution of if the build works.
The reason this screw up made it is simple. Cat did not foresee this being problematic when the workflow its a carbon copy of did not act up.