-
Notifications
You must be signed in to change notification settings - Fork 369
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.
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
.bazelignore the modules/ dir. #2270
Conversation
With the addition of overlays (bazelbuild#1566) it now can make sense to have BUILD and .bzl files inside the module version directories. However they don't necessarily make sense on their own. They are only supposed to work in the context of the source archive they overlay. To prevent issues like not being able to load() from a //:def.bzl that does not exit in the registry repo, let's just .bazelignore the modules/ dir.
We had Bazel test targets to validate the I think we need a more nuanced answer. In other repos I use |
And of course while the tests were disabled, two new packages were added that violate the schema:
|
They were accidentally disabled by bazelbuild#2270 Also fix the two broken metadata files which were added during the lapse.
They were accidentally disabled by bazelbuild#2270 Also fix the two broken metadata files which were added during the lapse.
They were accidentally disabled by bazelbuild#2270 Also fix the two broken metadata files which were added during the lapse.
With the addition of overlays (#1566) it now can make sense to have BUILD and .bzl files inside the module version directories. However they don't necessarily make sense on their own. They are only supposed to work in the context of the source archive they overlay.
To prevent issues like not being able to load() from a //:def.bzl that does not exist in the registry repo, let's just .bazelignore the modules/ dir.