-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix golint warnings #25
Comments
Sounds like a good plan. |
IMO, first, fixing all in one PR is OK; secondary, can we add |
@stewart-yu I think we may need to discuss what should be in vendor? files which are referenced by other codes OR files which are used during building, checking or testing? |
@maurya-anuj can you please help with this ? |
ping @sids-b @maurya-anuj Any updates? |
@m1093782566 , PR will be raised by @maurya-anuj for pkg folder next week. After which we can also add golint in CI |
fixed golint warnings in cmd beehive and pkg folder Fixes kubeedge#25
fixed golint warnings in cmd beehive and pkg folder Fixes kubeedge#25
fixed golint warnings in cmd beehive and pkg folder Fixes kubeedge#25
Fixed golint warnings in beehive, cmd, pkg folder Fixes kubeedge#25
Fixed golint warnings in beehive, cmd, pkg folder Fixes kubeedge#25
Fixed golint warnings in beehive, cmd, pkg folder Fixes kubeedge#25
Fixed golint warnings in beehive, cmd, pkg folder Fixes kubeedge#25
Fixed golint warnings in beehive, cmd, pkg folder Fixes kubeedge#25
Fixed golint warnings in beehive, cmd, pkg folder Fixes kubeedge#25
add owners file for beehive
Currently code in many directories (excluding
vendor
,docs
, etc.) fails to pass thegolint
.Contributors are very welcome to take part in this work. Just leave the directory you want to fix in this issue.
How to do it?
A simple way is
Then you'll see warnings if any. Just fix them accordingly.
/cc @m1093782566 @Lion-Wei @stewart-yu
The text was updated successfully, but these errors were encountered: