.bazelignore

# TODO(SERVER-81039): Remove once these can be compiled from the root directory.
src/third_party/grpc/dist
src/third_party/abseil-cpp/dist
src/third_party/prometheus-cpp
src/third_party/protobuf/dist
src/third_party/re2/dist
src/third_party/tcmalloc/dist
src/third_party/wiredtiger/dist
src/third_party/fuzztest/dist

# Ignore node_modules due to the following error
# ERROR: in verify_node_modules_ignored:
# pnpm install will create nested node_modules, but not all of them are ignored by Bazel.
# We recommend that all node_modules folders in the source tree be ignored,
# to avoid Bazel printing confusing error messages.
# 
# Either add line(s) to @//:.bazelignore:
# 
# node_modules
# 
# or disable this check by setting `verify_node_modules_ignored = None` in `npm_translate_lock(name = "npm")`
node_modules
src/mongo/db/modules/jstestfuzz/node_modules

# bazel_rules_mongo is consumed as a separate module via local_path_override
# (see //MODULE.bazel), so its packages must not ALSO be part of the main
# repo's package space — otherwise //buildscripts/... globs pick them up and
# their repo-relative labels like //utils:evergreen_git resolve against the
# main repo and fail.
buildscripts/bazel_rules_mongo

# These can cause issues in rules_lint
python3-venv
venv

.ijwb
.git

# This is not run by bazel at the moment
monguard

# Nested worktrees should be ignored
.claude/worktrees

# HermeticContainer and Linux container actions keep host-visible Bazel output roots, runtime
# state, and patched repository overlays under .tmp. Keep generated trees
# out of //... package expansion; they contain external repositories that are not
# valid packages in this workspace.
.tmp

# Convenience output paths may temporarily be directories while hermetic_container switches
# output roots. They are generated Bazel state, not source packages.
bazel-bin
bazel-mongo
bazel-out
bazel-testlogs