|
| 1 | +######################## |
| 2 | +# Import bazelrc presets |
| 3 | +import %workspace%/tools/preset.bazelrc |
| 4 | + |
| 5 | +# Don’t want to push a rules author to update their deps if not needed. |
| 6 | +# https://bazel.build/reference/command-line-reference#flag--check_direct_dependencies |
| 7 | +# https://bazelbuild.slack.com/archives/C014RARENH0/p1691158021917459?thread_ts=1691156601.420349&cid=C014RARENH0 |
| 8 | +common --config=ruleset |
| 9 | + |
| 10 | +# Bazel settings that apply to this repository. |
| 11 | +# Take care to document any settings that you expect users to apply. |
| 12 | +# Settings that apply only to CI are in .github/workflows/ci.bazelrc |
| 13 | + |
| 14 | +# Required until this is the default; expected in Bazel 7 |
| 15 | +common --enable_bzlmod |
| 16 | + |
| 17 | +# Ensure that the MODULE.bazel.lock file is complete and committed. |
| 18 | +# This is an important security measure: it ensures that developers on the |
| 19 | +# same rule set download dependencies at the same versions with the same bits. |
| 20 | +# This setting does not affect modules that depend on this module. |
| 21 | +# |
| 22 | +# When updating dependencies, use --lockfile_mode=refresh, for example: |
| 23 | +# bazel mod tidy --lockfile_mode=refresh |
| 24 | +# |
| 25 | +# When testing different versions of Bazel, use --lockfile_mode=update or |
| 26 | +# --lockfile_mode=off. The lock file format changes over time, and different |
| 27 | +# versions of Bazel may expect different syntax. Bazel also implicitly requires |
| 28 | +# some modules, and different versions have different dependencies, which |
| 29 | +# also affects the contents of the lock file. |
| 30 | +common --lockfile_mode=error |
| 31 | + |
| 32 | +# Load any settings specific to the current user. |
| 33 | +# .bazelrc.user should appear in .gitignore so that settings are not shared with team members |
| 34 | +# This needs to be last statement in this |
| 35 | +# config, as the user configuration should be able to overwrite flags from this file. |
| 36 | +# See https://docs.bazel.build/versions/master/best-practices.html#bazelrc |
| 37 | +# (Note that we use .bazelrc.user so the file appears next to .bazelrc in directory listing, |
| 38 | +# rather than user.bazelrc as suggested in the Bazel docs) |
| 39 | +try-import %workspace%/.bazelrc.user |
0 commit comments