How to replace Gazelle Go search with a convention for generated proto code?

[guw]

Our Gazelle runs in one workspace are slow. It looks like the slow down comes from generated code from proto files in Go.

The output I see is:

gazelle: finding module path for import github.com/org/repo/some/package/with/proto/foo/v1: go: -d flag is deprecated. -d=true is a no-op
go: downloading github.com/org/repo/ v1.2.3
go: downloading github.com/org/repo/some/package v4.5.6
go: module github.com/org/repo/some/package@upgrade found (v4.5.6), but does not contain package github.com/org/repo/some/package/with/proto/foo/v1

We have the following directives in the root BUILD.bazel file:

# gazelle:prefix github.com/org/repo
# gazelle:proto disable

This is because the proto files we process/build with our own macro. The macro sets up proto_library, go_proto_library (regular and second one with @com_connectrpc_connect//cmd/protoc-gen-connect-go:protoc-gen-connect-go go_proto_compiler plugin), ts_proto_library and buf_lint_test.

We maintain the BUILD.bazel files for proto files manually.
We also (have to) maintain the dependencies to generated Go/TS code manually like this:

go_library(
    ...
    deps = [
        ...
        "//some/package/with/proto/foo/v1:bar_connect_go_proto",  # keep: generated by macro
    ],
)

I am looking for some recommendations/guidance on improving this setup.

1. Whenever Gazelle does the finding module path for import it takes a long time. This is unnecessary. Can I instruct Gazelle to stop searching for this prefix?

2. I would like to find a way to auto-generate the proto BUILD files as well as the Go dependencies. I think a convention should work. Is there any doc/guidance on setting this up? Do I need to write my own Gazelle extension for this?