Set --incompatible_strict_conflict_checks=false #1771
Merged
+2
−0
Conversation
This file contains 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
keith
force-pushed
the
ks/set-incompatible_strict_conflict_checks-false
branch
from
e4f8399
to
8917b5b
Compare
keith
requested review from
BalestraPatrick,
brentleyjones,
segiddins and
thii
as code owners
thii
approved these changes
Nov 29, 2022
keith
added a commit
that referenced
this pull request
Nov 29, 2022
Reverts #1771 This was reverted in bazel for now, so in case it's flipped again we want CI to catch it
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.
bazelbuild/bazel#16729 (comment)