Jay Conrod

#41583 is an accepted proposal for a `go test -skip` flag that sounds similar. What about bringing that to `go generate`?

I think the issue was that we don't really know at analysis time (before reading source files) what the imports will be in the generated go files. Is that roughly...

Sorry for taking so long to respond on this. The repeated error messages are certainly not a good experience. When Gazelle resolves an import path to a dependency outside of...

Note to anyone reading, checksum errors are serious and you shouldn't workaround them without understanding why they happened. Usually, this is caused by a module author rewriting a version tag....

This directive hasn't been implemented. Is this a `go_test` that ends up broken or something else? Sorry I don't know enough about jsonnet to advise. Good luck though.

rules_go just supports Go and proto. I avoid adding support for too many other tools, since it adds dependencies for users. I'm sure CEL rules could be written for Bazel,...

@dragonsinth No this is still open. Feel free to send a patch. I changed the directive name in the first comment from `skiprule` to `skip`. For the example you gave,...

I can see an argument for not requiring `# keep` for labels within `srcs`, but it does add some complexity. Gazelle treats `srcs` like any other mergeable attribute. When it...

> I was surprised that gazelle takes ownership over sources that it definitely didn't write in the first place. In general, we can't distinguish between values that should be deleted...

A `gazelle:generates` directive seems fine as a general solution. For file embedding specifically, I expect that after Go 1.16 ships, and rules_go and Gazelle get support for `//go:embed` directives (bazelbuild/rules_go#2775,...