Fabian Meumertzheim

The docs exist, they just aren't sufficiently discoverable: https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/bzlmod.md @tyler-french What do you think, is it time to make the Bzlmod instructions the default?

> Or should I have one single MODULE.bazel for the entire monorepo at the WORKSPACE level (as suggested in the tutorial)? I would say that a monorepo should really have...

You are affected by this bug: https://github.com/bazelbuild/bazel/issues/20721 Could you try again with Bazel 7.0.1rc1?

That error means that you need to update the `load` in your top-level BUILD file to be from `gazelle` rather than `bazel_gazelle`. You can of course keep using the old...

That failure is expected, you aren't declaring any external dependencies. That is what the `go_deps` extension is for, see https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/bzlmod.md#external-dependencies.

This looks reasonable to me, but we should only allow "global" `gazelle_overrides` *before* any non-global ones, otherwise the precedence rules will be confusing. I wonder whether this would be the...

> Are you referring to the ordering of any go_deps.gazelle_override declarations in MODULE.bazel? Yes, that's what I meant. The order of the individual `tags` corresponds to declaration order in the...

@tyler-french I also dislike "order matters", I'm just not sure about the right way to enforce it. I would find a `MODULE.bazel` file with: ```starlark go_deps.gazelle_override(...) go_deps.default_gazelle_override(...) go_deps.gazelle_override(...) ``` almost...

What would you expect to happen instead? I would say that this behavior is pretty much expected in this mode. Could you try whether extracting the function to a non-`_test.go`...

CC @shahms who contributed this feature