add '.bazel' to extension list #407
Merged
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
Improve support for Bazel files by adding `.bazel` to the extension list to support files like `MODULE.bazel`, `WORKSPACE.bazel`, etc.
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.
Improve support for Bazel files by adding
.bazelto the extension list forWORKSPACE.bazeland the newMODULE.bazelfile. As a cleanup this also lets me takeBUILD.bazelout of the filenames list.Also it's reasonably common to use files names like
BUILD.library_name_here.bazel(example here) - this also supports those files which is nice (related to #103 since that's an alternate naming convention for the same thing).