Thomas

@UebelAndre Would you mind checking out my branch and trying it out? It's not feature complete, though rules_rust builds with it (`bazel builld //...`) and we're also now using it...

https://github.com/golang/go/issues/28592

> Hey, I haven't done a real pass through this code yet but did see a ton of deletion I didn't expect. Why wouldn't this change initally be a new...

> > The approach taken in this change differs dramatically as the build files aren't rendered, but instead interpreted which makes it fundamentally incompatible with the existing approach. Maintaining both...

I'm back from holiday. Would you like to have a design discussion? It would be good to understand the problems and limitations with current system, what an ideal system would...

We ran into this too. We worked around this with: ###### third_party/io_docker_index_library_postgres/BUILD.bazel ``` load("@io_bazel_rules_docker//container:container.bzl", "container_image") # A weird hack which gives the image a unique tag. container_image( name = "image",...

We maintain an internal patch for nogo which shows suggested fixes, which is half way there really. The patch applies the suggested fix and then displays the diff. The only...

@sluongng It's not perfect, but it does seem to work. https://gist.github.com/uhthomas/fb66757f0e38e143bc465189a3b3d2ad

Maybe useful? https://github.com/apps/publish-to-bcr

There is a difference between `vet = True` and the TOOLS_NOGO variable. TOOLS_NOGO should include all analysers as I understand.