Jay Conrod

I need to tag a release shortly, but I'd like to do at least part of this before then. These points seem straightforward and clearly good ideas: * Pass GOPROXY,...

This is likely coming up due to Gazelle's [dependency resolution](https://github.com/bazelbuild/bazel-gazelle#dependency-resolution). In short, Gazelle needs to resolve imports in .go files to the corresponding Bazel label. It first looks at library...

`update-repos -from_file=go.mod` loads module information with `go list -m all`. It also can run git commands, depending on your `GOPROXY` setting. Again, I'd expect it to find and use your...

I couldn't reproduce this locally. Not sure if I followed quite the same steps. * In your repository, I changed `github.com/stevenwjy/new-private-test` to `github.com/jayconrod/modtest` (a scratch repository I made private) *...

Cool, glad it's fixed. Leaving this issue open, since Gazelle may need to do something with `GOSUMDB`. It's not clear to me that it's all that necessary for dependency resolution,...

I'll vouch. Everyone in @bazelbuild/go-maintainers should probably have access.

This seems pretty reasonable. Gazelle doesn't have a really well-defined policy on error handling or exit codes. Being unable to parse a build file seems like it should be a...

Sorry, I don't have bandwidth to review at this time. cc @bazelbuild/go-maintainers in case someone else can take a look.

I opened bazelbuild/bazel#8670. I believe it's a bug in coverage.

@meteorcloudy The issue was bazelbuild/bazel#8670. The fix is cherry-picked in bazel 0.27.1.rc1, and I've verified it fixes rules_go CI ([log](https://buildkite.com/bazel/rules-go-golang/builds/1222#da7ba059-d9d8-40ab-a0a7-ec72dbe968c6)).