From 44a842d4193330a85d51120811b6d0aa9bcf1a7d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9gis=20Desgroppes?= Date: Thu, 15 Jan 2026 13:27:51 +0100 Subject: [PATCH] Fix `bazel:mod-tidy` job to ignore lockfile changes The `bazel:mod-tidy` job is meant to ensure `MODULE.bazel` remains in an optimal state (not only in `bazel`'s opinionated format, but also to help maintain the `use_repo` directives that Gazelle will update). The problem is that I added it without thinking it could fail due to `MODULE.bazel.lock` being updated by side effect, which is already (and better) guarded by the sibling `bazel:mod-deps` job. Adding `--lockfile_mode=off` to `bazel mod tidy` is therefore meant to prevent `bazel:mod-tidy` from failing on lockfile changes for a proper separation of concerns, distinct hints being provided. --- .gitlab/build/bazel/lint.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab/build/bazel/lint.yml b/.gitlab/build/bazel/lint.yml index 6e992c6dfedc..9282fb45986e 100644 --- a/.gitlab/build/bazel/lint.yml +++ b/.gitlab/build/bazel/lint.yml @@ -19,7 +19,7 @@ bazel:mod-tidy: extends: .bazel:runner:linux-amd64 stage: lint script: - - bazel mod tidy + - bazel mod tidy --lockfile_mode=off - git diff --exit-code after_script: - |-