made --incompatible_tags_propagation to be true by default (only star… #9076
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
…lark rules affected)
ishikhman
requested review from
brandjon,
c-parsons,
dslomov,
laurentlb and
vladmos
as code owners
|
Closing, because flag flip is not stable. |
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.
--incompatible_allow_tags_propagationflag protects the tags propagation from targets to actions.RELNOTES: bazel will take tags specified on target level, filter them based on prefix and propagate to the actions, that are created for the target. Propagated prefixes: "block-", "requires-", "no-", "supports-", "disable-", "local", "cpu:". Only Starlark rules affected. See #8830 for details.