Fabian Meumertzheim

Previous discussion on this topic: https://gist.github.com/fmeum/c87c183ad6ffc55add0ca04232761ea1 ``` go_repos = go_deps.from_file(go_mod = "//:go.mod") use_repo(go_deps, *go_repos) ``` can't quite work since tags in `MODULE.bazel` are just metadata, they don't invoke any actual...

That's a very good point, I didn't think about the implications for extension evaluation. I thought about alternative solutions and had an idea: How about having a Bazel module `auto_use_repo`...

I created [`auto_use_repo`](https://github.com/fmeum/auto_use_repo). The README links to a Gazelle PR that adds support for it to `go_deps`.

@saraadams The Windows failure should go away if you rebase on master.

@tetromino Would you be available to review this? My motivation for suggesting to add this is two-fold: 1. Without https://github.com/bazelbuild/bazel-skylib/issues/290, it is essentially impossible to write custom asserts (e.g. `assert_fails`)...

@sgowroji Since I'm working on a bit of a larger change, I'm already using the CI to catch potential issues. There is no need to assign a reviewer yet as...

@gregestren Thanks for your feedback! I will likely not be able to get back to it until after BazelCon and the Bazel 6 release, put will pick this up right...

I just had an idea that may obviate the need for new Starlark API. I will give it a try and update the PR if it works.

@gregestren @aranguyen As we discussed at BazelCon, I pushed a new version of this PR that is stripped down to the essentials. Most of the commits are the same, with...

@katre No need to do anything, I simply can't override the default reviewers.