Update .bazelrc #174
Merged
Update .bazelrc #174
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
Make sure that no regressions are introduced to build with incompatible_disallow_empty_glob
56 tasks
joeleba
approved these changes
Feb 19, 2024
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.
Make sure that no regressions are introduced to build with incompatible_disallow_empty_glob
What this PR does and why we need it:
It makes sure that this repository can be built with incompatible_disallow_empty_glob and it works in the moment that incompatible_disallow_empty_glob is enabled by default
New changes / Issues that this PR fixes:
It contributes to bazelbuild/bazel#15327
Special notes for reviewer:
See bazelbuild/bazel#15327 for more details
Does this require a change in the script's interface or the BigQuery's table structure?
I expect no