Jay Conrod

It's cool that you have Gazelle working for Elixir. Do you have a repo up anywhere? If so, I'd be happy to add it to [Supported languages](https://github.com/bazelbuild/bazel-gazelle/blob/master/extend.rst#supported-languages) (or feel free...

@fweikert What are the plans? In case it's useful, rules_go has a [release process](https://github.com/bazelbuild/rules_go/wiki/Release-process) but little automation. To summarize: * We maintain two or three stable release branches. I cherry-pick...

About packaging for rule users: I've been thinking about something like this for integration testing. There could be some target that packages rules and supporting tools and libraries, then extracts...

cc @bazelbuild/go-maintainers The history until now: * Gazelle was originally part of rules_go. It had hard coded support for Go. * It moved to this repository so that rules_go could...

> We could help out with the maintenance in some way. I imagine we can use a "contrib" model where some subfolders here are documented as being owned and maintained...

@achew22 Ah, looks like you're right. I don't think I actually knew that was fixed. So maybe this isn't as difficult as I'm thinking. What would actually be needed for...

Seems useful, but I'm hesitant to support this because it opens the door to a lot of other bespoke customizations. I'd prefer to keep `go_repository` focused on retrieving Go code...

I suspect you're running into bazelbuild/bazel-gazelle#890, also described in bazelbuild/bazel-gazelle#892 and bazelbuild/bazel-gazelle#982. Could you try setting ~`build_file_naming_convention = "go-default_library"`~ `build_file_naming_convention = "go_default_library"` on `com_github_envoyproxy_protoc_gen_validate` and any other repositories that have...

Sorry to be slow to get back to this. `build_file_naming_convention` should be `"go_default_library"`, not `"go-default_library"`. Sorry for the typo... though I'm surprised nothing reported an error because of that. Could...

Sorry, it looks like this still needs some debugging, but unfortunately I don't have bandwidth to look into it yet. I would have expected your `go_repository` declaration from [this comment](https://github.com/bazelbuild/bazel-gazelle/issues/988#issuecomment-777725731)...