feature request: add option to automatically fix issues

[afeld]

Hello! I'm relatively new to Go, coming from the Ruby world. I'm using golint, but noticed that the errors need to be fixed manually. Ruby's RuboCop linter provides a --auto-correct flag, where it can fix some of the simple lint warnings by itself. Even for simple warnings (e.g. func getXmlDoc should be getXMLDoc), this would be useful. Maybe rename can be used?

Thanks!

[donce]

Totally agree - the tool doesn't have to cover many rules, but just covering a few simple rules would help a lot for migrating go codebases to be lint-compatible! :)

[macnibblet]

I would love to see this too

[manesioz]

Any updates on this feature? Would be really great to have.

[david-nyt]

Would love this feature!

[mvdan]

Thank you for submitting this issue! As per golang/go#38968, we are freezing and deprecating golint. There's no drop-in replacement to golint per se, but you should find that Staticcheck works well in encouraging good Go code, much like golint did in the past, since it also includes style checks. There's always gofmt and go vet too, of course.

If you would like to contribute further, I'd encourage you to engage Staticcheck's issue tracker or look at vet's open issues, as they are both actively maintained. If you have an idea that doesn't fit into either of those tools, you could look at other Go linters, or write your own - these days it's fairly straightforward with go/analysis.

To help avoid confusion, I'm closing all issues before we freeze the repository. If you have any feedback, you can leave a comment on the proposal thread where it was decided to deprecate golint - though note that the proposal has been accepted for nearly a year. Thanks!