[proposal] migrate to golangci-lint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 196
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
I'm happy to do this work, but thought I'd open it as an issue first to see if you're even interested in the change. I propose a swap over to [golangci-lint](https://github.com/golangci/golangci-lint) over gometalinter.
The two main reasons for this change are:
* It's substantially better performing, works better in a Go 1.11 ecosystem (although they're still working with some linters to get them up to snuff, so it's a work in progress)
* [Can be installed via shell][1], which improves usage and start time in CI and Docker
I could list more reasons, but at that point it's just getting to my personal thoughts on one tool over another.
Would you be open to me swapping the tools out? For the first
[1]: https://github.com/syntaqx/serve/blob/master/.travis.yml#L11
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .travis.yml at line 11 and review how gometalinter is installed and invoked. Compare the current CI and Docker linting setup with golangci-lint, then consider the migration complete when the replacement runs successfully in those workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100