Fabian Meumertzheim

@tyler-french What do you think, are there any footguns in allowing multiple `go.mod` files per module? Proper `go.work` support would of course be more involved.

A true monorepo would only have a single `MODULE.bazel` and a single `go.mod` file. If you would like to still have multiple `go.mod` files, you might be interested in `go.work`...

If I check out `rules_python` and update the Gazelle version in `examples/build_file_generation` to `v0.32.0`, running `bazel run //:gazelle` in that directory succeeds. Could you check whether you are using the...

I can reproduce it now, I was on an older commit when I first tried this.

I can reproduce this with Gazelle up to v0.32.0, but not with v0.33.0. I think that it was fixed by https://github.com/bazelbuild/bazel-gazelle/commit/e3deb49b65ad8d7ec6cbc54b7ff511a537f8de56. @aignas It looks like some `:gazelle` target in `rules_python`'s...

Maybe we should just make `gazelle:proto disable` and `build_file_generation = "on"` the global defaults for Gazelle? @linzhp has brought that up before.

We definitely need something like this, but I think the result would be much better if it was a universal mechanism. Could you add a comment on https://github.com/bazelbuild/bazel/issues/17880 to revive...

Thanks for bringing this up, the way we currently maintain a cache in a repo outside of Bazel's control has always made me uneasy. A mid- to long-term alternative could...

@jayconrod Could you review this? You are in the best position to determine whether this is safe to delete.

@linzhp @achew22 What do you think about the tradeoff here? I could test out the error message and add it to the docs or I could keep this code and...