-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review use of nolint
directives across code
#2384
Comments
/help |
@killianmuldoon: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
I can take this task as I have done similar work previously. 😄
|
I can pick this one:
|
I can pickup |
I can pick |
Will pick |
@killianmuldoon Also I see other linters have only occurrences <=2, can we combine them in same PR? Since the changes wont be significant. |
Will pick rest of the linters: |
@killianmuldoon |
#2399 seems to be the last open PR for this 🎉 |
Looks like we've ticked everything off the list here - thanks a lot for all the effort folks! |
CAPV uses many linters from golangci-lint, but many of these linters are skipped in some packages due to the use of
nolint
directives. The usage of these should be reviewed and as many as possible should be removed. This work should be tackled as a follow-on from #2058Some initial findings:
gocritic
#2399The above usages should be investigated and we should remove where possible. Where not possible we should add comments beside the lint ignore directives explaining why these linters are ignored.
The text was updated successfully, but these errors were encountered: