Jay Conrod

@asv This is something I wish were simpler in Bazel. You can build with the command line argument `--output_groups=go_generated_src` (or any comma separated list of group names). To get the...

I don't believe anyone is working on this at the moment. This should eventually done by either me or someone who maintains `com_google_googleapis`. I'd rather not take PRs from anyone...

Tentatively tagging this for the next release. I've reached out to some of the folks developing these generators to understand how these should be supported through rules_go and Gazelle.

@ghasemloo Continuing discussion here from #2587: As I mentioned earlier, I'm not sure whether `google.golang.org/grpc/cmd/protoc-gen-go-grpc` is stable. It's checked into the master branch, but it's in its own submodule which...

The main `protoc-gen-go-grpc` confirmed it's still under development, and while they're aiming for a release in a few months, they anticipate breaking change before then. I'll drop this from the...

@PaulSonOfLars Thanks for the heads up! Adding to `v0.25` milestone.

@ghasemloo Not yet I'm afraid. cc @bazelbuild/go-maintainers Anyone interested in working on this?

The main thing is `go_proto_compiler` targets need to be defined, wrapping the `go_binary` targets for these generators and declaring packages they import from generated code. The `go_proto_compiler` targets for APIv1...

[Avoiding Conflicts](https://github.com/bazelbuild/rules_go/blob/master/proto/core.rst#avoiding-conflicts) has some info on resolving conflicts like this. If you want to use pre-generated .pb.go files and not generate them at build time, use `build_file_proto_mode = "disable_global"` on...

> I actually also tried adding # gazelle:proto disable_global in my //BUILD.bazel file, but that stops generating any go_library build rules for my protos, which is something I do want...