Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[6.0.0] Default --incompatible_strict_conflict_checks to true. #16864

Merged
merged 1 commit into from
Nov 28, 2022
Merged

[6.0.0] Default --incompatible_strict_conflict_checks to true. #16864

merged 1 commit into from
Nov 28, 2022

Commits on Nov 28, 2022

  1. [6.0.0] Default --incompatible_strict_conflict_checks to true. 

    The downstream pipeline indicates that this is safe to flip: https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/1346

Fixes bazelbuild#16729.

RELNOTES[INC]: `--incompatible_strict_conflict_checks` is flipped to true. See bazelbuild#16729 for details.

PiperOrigin-RevId: 491324038
Change-Id: Iea8951867fa20f2aa1a67bf3ba3c86c26e4292de
    @tjgq
    tjgq committed Nov 28, 2022
    Configuration menu
    Copy the full SHA
    147353f View commit details
    Browse the repository at this point in the history