Gazelle: make exclude directive work in subdirectories #1107
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
'# gazelle:exclude' directives can now contain paths, not just file and directory base names. For example, if you add the directive '# gazelle:exclude vendor/example.com/foo/testdata' in your root build file, it will be as if the directive '# gazelle:exclude testdata' were written in vendor/example.com/foo/BUILD.bazel. Fixes bazel-contrib#415
ianthehat
approved these changes
Dec 5, 2017
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.
'# gazelle:exclude' directives can now contain paths, not just file
and directory base names. For example, if you add the directive
'# gazelle:exclude vendor/example.com/foo/testdata' in your root build
file, it will be as if the directive '# gazelle:exclude testdata' were
written in vendor/example.com/foo/BUILD.bazel.
Fixes #415