nogo Issues

[albertocavalcante]

This aims to be an umbrella issue for current reported issues with nogo. Please let me know if there are objections with this approach.
I think would also be helpful to a nogo label to apply to issues and make it easier to filter. Related to that would be nice to be able to differentiate between bugs and feature requests.

I will update here based on this simple query:

https://github.com/bazel-contrib/rules_go/issues?q=is%3Aissue%20state%3Aopen%20is%3Aunlocked%20%22nogo%22

Bug Reports

• nogo broken with ".facts" errors in 0.50.0 #4084
• nogo not populating Go version in analysis pass #3924
• nogo 1.18/1.19 #3230
• nogo error with Golang 1.20 #3452
• nogo: golink uses the wrong cc linker on MacOS with DEVELOPER_DIR set #3826

Feature Requests

• Enhance nogo to provide warnings and export diagnostics #4273

Bzlmod

• nogo: exclude_files requires hardcoding external bzlmod paths #4284

Questions

• Question: Can I use nogo to make linter more faster? #3194
• [nogo] How to specify and include specialized linter config files? #3234