From c1925e5c619db095bac75362d305efd4ee5c4d42 Mon Sep 17 00:00:00 2001 From: Joseph Lisee Date: Tue, 19 Sep 2023 10:25:18 -0400 Subject: [PATCH] Update bzlmod migration to mention enable_bzlmod When following the migration guide make sure to explicitly tell the user to update their `.bazelrc` with the `--enable_bzlmod` so that Bzlmod will be active. --- site/en/external/migration.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/site/en/external/migration.md b/site/en/external/migration.md index fdfb6435c27e60..cd1638cb45785c 100644 --- a/site/en/external/migration.md +++ b/site/en/external/migration.md @@ -32,6 +32,19 @@ your workspace root, maybe with comments like: # See MODULE.bazel for external dependencies setup. ``` +### Enable Blzmod in your bazelrc {:#enable-bzldmod} + +`.bazelrc` lets you set flags that apply every time your run Bazel. To enable +Bzlmod we use the `--enable_bzlmod` flag, and apply it to the `common` command so +it applies to every command: + +* **.bazelrc** + + ``` + # Enable bzlmod for every bazel command + common --enable_bzlmod + ``` + ### Specify repository name for your workspace {:#specify-repo-name} * **WORKSPACE**