There's no linter in CI. go vet runs implicitly via go test, but that's about it.
I ran golangci-lint with its default linters against the repo and got ~55 findings. Nothing urgent, but these accumulate. A linter in CI catches them at PR time.
Proposal
- Add a minimal
.golangci.yml using only the default linters.
- Fix or
//nolint existing findings so main passes clean.
- Add a
lint Makefile target.
- Add a CI job using golangci-lint-action, parallel to the existing test job.
There's no linter in CI.
go vetruns implicitly viago test, but that's about it.I ran golangci-lint with its default linters against the repo and got ~55 findings. Nothing urgent, but these accumulate. A linter in CI catches them at PR time.
Proposal
.golangci.ymlusing only the default linters.//nolintexisting findings so main passes clean.lintMakefile target.