-
Notifications
You must be signed in to change notification settings - Fork 160
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
Add support for golint #168
Conversation
Signed-off-by: Marcelo Amaral <marcelo.amaral1@ibm.com>
Signed-off-by: Marcelo Amaral <marcelo.amaral1@ibm.com>
thanks, would you add this to GH action next? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -136,6 +136,9 @@ test-verbose: ginkgo-set tidy-vendor | |||
format: | |||
gofmt -l -w pkg/ cmd/ | |||
|
|||
golint: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need lint before build?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for ex
_build_containerized: format golint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but since we have many problems now it will be very annoying!
So, after we fix the issues, we can add lint as a requisite for building...
Using linters improves the code quality and readability by highlighting problems before they are executed, and it helps with the standardization of the codebase.
This PR enables golint. But, fixing the issues is out of the scope of this PR and will be done in another PR.
Additionally, this is PR is part of the effort for testing the code quality, as describe in the issue #161
Signed-off-by: Marcelo Amaral marcelo.amaral1@ibm.com