Skip to content

fix: manually ignore bazel-* directories to make using custom Bazel builds easier #1181

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 8, 2023
Merged

fix: manually ignore bazel-* directories to make using custom Bazel builds easier #1181

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .bazelignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Normally these are ignored, but if you're using a custom
# build of Bazel with a custom --output_user_root value, Bazel
# tries to follow the symlinks of the other builds and finds
# the WORKSPACE, BUILD, etc files and tries to build them.
bazel-rules_python
bazel-bin
bazel-out
bazel-testlogs