Closed CecileRobertMichon closed 3 years ago
/help /good-first-issue
@CecileRobertMichon: This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
Hey @CecileRobertMichon, I am new to open source and trying to learn to contribute. I would love to work on the issue. Just a quick question, do we just need to change the .golangci.yml
file? And under that, do I just need to change enable-all -> disable-all
and enable -> disable
? Or do I need to look over additional stuff?
@ShrillShrestha you should only have to change the .golangci.yml
. The goal is to change the configuration syntax but to keep the exact same linters enabled. You can see which ones are currently enabled by running make lint
:
INFO [lintersdb] Active 33 linters: [asciicheck bodyclose deadcode depguard dogsled errcheck goconst gocritic gocyclo gofmt goimports golint gomodguard goprintffuncname gosec gosimple govet ineffassign maligned misspell nakedret nolintlint prealloc rowserrcheck scopelint staticcheck structcheck stylecheck testpackage typecheck unconvert unparam varcheck]
I recommend running it before and after changing the configuration to using "enabled" to make sure the linters haven't changed.
Thank @CecileRobertMichon, I will try to make that changes. I will let you know if I have further questions.
https://github.com/kubernetes-sigs/cluster-api/blob/master/.golangci.yml currently uses
enable-all: true / disable: [...]
We should switch it to use
disable-all: true / enable: [...]
.The golangci-lint documentation states:
https://golangci-lint.run/usage/configuration/