-
Notifications
You must be signed in to change notification settings - Fork 63
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 Golang linting in CI and remove unreachable code from the repo #184
Comments
Hey @akshay196 I would like to work on this issue. |
@bhavyastar Thanks for showing interest.
Feel free to fix all at once or take a sequential approach. Let us know if you need any help. |
@akshay196 Is the issue fixed, or can I work on this? |
@bhavyastar Are you still working on this issue? |
@theluckiesthuman If you're interested, you can get started on this. Let us know if you need anything. |
@akshay196 Please assign me this. |
@akshay196 can i work on this ? |
@theluckiesthuman Are you still working on this? |
@karthikmurali60 Feel free to take it up and raise PR once done. |
Hi @akshay196 I want to work on this issue! |
@Omkar0114 You can use automatic fix option of golangci-lint. Hope this is clear. Feel free to raise PR. |
@akshay196 Sure. I'll raise a PR soon. Also, I want to ask if we create the |
@Omkar0114 let's add lint check in go.yml itself. |
Cool. Thanks @akshay196 |
This issue is open for anyone interested. Partial PR for a reference #253 |
Hi, @akshay196 I would like to work on this. |
Hey @jaydee029 Feel free to start working. No one actively working on it right now. |
@akshay196 I'm assuming we resolve all the linting errors not just the unused func/types error? right? |
If this is true, we would need to make certain structural changes such as error handling, since lot of the errors involved are missing error checks, as well as the way in which for loops are structured etc. |
@jaydee029 sure, lets try to resolve all possible linting errors. |
@jaydee029 Thanks for your contribution. We have now added golangci-lint to GitHub workflows. |
Describe the issue you're facing
The text was updated successfully, but these errors were encountered: