Brandon Lico

I suppose we could explicitly pass in `-mod=readonly` when Gazelle runs `go list` here: https://github.com/bazelbuild/bazel-gazelle/blob/master/repo/remote.go#L430. Although `mod=readonly` is set by default for `go list`, I assume `GOFLAGS` overrides that behavior.

I agree this feature would be valuable, but I worry about the introduced complexity and new types of error scenarios that come with managing a cached index. Especially given the...

My main concern is that to run `buildozer` as part of `go_repository` we would need to vendor all of its code and compile it with `go`, similar to what we...

So if I am understanding the proposal correctly, it is to cache a patch file of Gazelle generations for each repository, with `sha256`/`sum` being the key. Aren't the majority of...

@sluongng You mention you are optimizing for your p50 CI times here, do your CI nodes keep a Bazel output_base cache between runs, or does every run use a "fresh"...

With #1201 it took me only 16s to cleanly fetch `github.com/docker/docker`. Although not as fast as the patch file approach, the PR provides an immediate speed-up for all `go_repository` rules...

This is expected behavior. Gazelle doesn't generate a BUILD file under the directory you are trying to import (`github.com/actgardner/gogen-avro/v10`) because it contains [no go code](https://github.com/actgardner/gogen-avro/tree/master/v10) to be imported. I tested...

@alice-ks Given that Gazelle is a standard tool for Golang Bazel-based workflows (everywhere outside of Google that is), what are your thoughts on integrating Gazelle into Go-based workflows for the...

@jayconrod I would like to hear your feedback on another approach we have thought of for our monorepo, to help go modules work with generated packages. So like you said,...

Our idea right now is to: 1. `bazel query --output=proto //...:*` to find all of the non-external `srcs` and `importpath` attributes known to Bazel. 2. Read all of the imports...