diff options
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | 2023-12-25 11:31:23 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-25 10:31:23 +0000 |
| commit | 988ccdda90f75ba17e50765d8737ad44e7e829c4 (patch) | |
| tree | 55df770cc54f2091a2b129cab3e484dcae429484 | |
| parent | e289d100eff04070481754b5bdbb2d402c5cf763 (diff) | |
| download | bazelbuild-rules_go-988ccdda90f75ba17e50765d8737ad44e7e829c4.tar.gz | |
Link to the isolated extension usages issue in Bzlmod guide (#3800)
| -rw-r--r-- | docs/go/core/bzlmod.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/go/core/bzlmod.md b/docs/go/core/bzlmod.md index d3cb4168..5be579aa 100644 --- a/docs/go/core/bzlmod.md +++ b/docs/go/core/bzlmod.md @@ -180,7 +180,7 @@ If you need to depend on Go modules that are only used as tools, you can use the 2. Run `bazel run @rules_go//go mod tidy` to populate the `go.mod` file with the dependencies of the tools. -Instead, if you want the tools' dependencies to be resolved independently of the dependencies of your regular code (experimental): +Instead, if you want the tools' dependencies to be resolved independently of the dependencies of your regular code ([experimental](https://github.com/bazelbuild/bazel/issues/20186)): 2. Run `bazel run @rules_go//go mod init` in the directory containing the `tools.go` file to create a new `go.mod` file and then run `bazel run @rules_go//go mod tidy` in that directory. 3. Add `common --experimental_isolated_extension_usages` to your `.bazelrc` file to enable isolated usages of extensions. |