-
Notifications
You must be signed in to change notification settings - Fork 4
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
Determine which sub-linters should be enabled or disabled #66
Comments
trym-b
added a commit
that referenced
this issue
Feb 27, 2024
# Motivation A lot of sub-linters are disabled by default when using `golangci-lint`. This commit now makes it explicit which sub-linters are used and which ones are not. All of the sub-linters that failed has been disabled. Introduces #66
trym-b
added a commit
that referenced
this issue
Feb 27, 2024
# Motivation A lot of sub-linters are disabled by default when using `golangci-lint`. This commit now makes it explicit which sub-linters are used and which ones are not. All of the sub-linters that failed have been disabled. Introduces #66
trym-b
added a commit
that referenced
this issue
Feb 27, 2024
# Motivation A lot of sub-linters are disabled by default when using `golangci-lint`. This commit now makes it explicit which sub-linters are used and which ones are not. All of the sub-linters that failed have been disabled. Introduces #66
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not all of the sub-linters of
golang-ci
should be used, and this issue needs to determine what errors should be fixed, and which ones should be left disabled.The text was updated successfully, but these errors were encountered: