Open gold-kou opened 4 years ago
I think this would be a nice addition to the CI pipeline. golangci is a stable enough and standard enough tool that I would feel comfortable pulling it in. It should help us find additional bugs as well as cleanup and simplify the codebase.
I envision the steps for implementing golangci-lint being:
gofmt
and go vet
in the CI pipeline with golangci-lint.Does that sound reasonable?
@rmulley Thank you for your reaction. 😄
I agree step by step introducing for safe.
However, I couldn't understand that well. In your idea, PR should be divided?
@gold-kou I'm saying we should strive to keep builds passing, and avoid very large Pull Requests. To do that we should incrementally bring in golangci-lint and add additional linters. It should not all be done in one step or one PR in my opinion.
Hello. Now, only used vet and fmt as linters. It's not a problem but we can use more linters by golangci-lint. It might be better to introduce more linters as some maintainers now.
This is a sample result of local. (default setting)
Could you tell me how do you feel about this? I feel it deserves to try in this repo.
If we keep using Travis, this article might be helpful. https://medium.com/@classik19881/ci-continuous-integration-with-travis-ci-for-golang-project-532d1d1fc7b6
Or we can use other CI tools such as CircleCI or Actions.
Thank you.