-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
staticcheck violations tracking issue #13877
Labels
Component: General
Changes throughout the code base
Type: Enhancement
Logical improvement (somewhere between a bug and feature)
Type: Internal Cleanup
Comments
ajm188
added
Type: Internal Cleanup
Type: Enhancement
Logical improvement (somewhere between a bug and feature)
Component: General
Changes throughout the code base
labels
Aug 29, 2023
|
This was referenced Aug 29, 2023
The nuance is that according to https://golangci-lint.run/usage/linters/
|
This was referenced Aug 29, 2023
Merged
Assuming everything has been tidied up based on last PR's title. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component: General
Changes throughout the code base
Type: Enhancement
Logical improvement (somewhere between a bug and feature)
Type: Internal Cleanup
Feature Description
Ideally,
staticcheck ./go/...
would report 0 violations, this issue is meant to track our violations so we can gradually work down to zero. It's likely too long to fit into the description length limit, so I will add a comment with the current state after opening.Use Case(s)
Code cleanliness, style issues, cleanup of dead code and deprecated library functions, and so on.
The text was updated successfully, but these errors were encountered: