The golangci-lint configuration file contains some customized linter configurations, simply because not all of the linters that are enabled by default are worth it.
The "ci" workflow has also been modified a little. Namely, building the binary is done first as a quick and inexpensive check. If it successfully builds, then we go on to do the full-bore vet, staticcheck, linting, and tests.
General:
[x] Have you removed all sensitive information, including but not limited to access keys and passwords?
[x] Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?
Pull Request Guidelines:
[x] Does your submission pass tests?
[ ] Have you added tests?
[x] Are you addressing a single feature in this PR?
[x] Are your commits atomic, addressing one change per commit?
[ ] Are you following the conventions of the language?
[ ] Have you saved your large formatting changes for a different PR, so we can focus on your work?
[x] Have you explained your rationale for why this feature is needed?
The golangci-lint configuration file contains some customized linter configurations, simply because not all of the linters that are enabled by default are worth it.
The "ci" workflow has also been modified a little. Namely, building the binary is done first as a quick and inexpensive check. If it successfully builds, then we go on to do the full-bore vet, staticcheck, linting, and tests.
General:
Pull Request Guidelines: