-
Notifications
You must be signed in to change notification settings - Fork 6
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 golangci-lint configuration and appease some linters #13
base: master
Are you sure you want to change the base?
Conversation
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.
Your linting PR was made against master, but I reworked the cli
package in the relive
branch, you should lint that branch instead.
I don't understand: this PR is a standalone change that has little to do with the CLI overhaul. As such, it should generally go into master. |
You linted |
Should you not like the "temporary master branch" approach but prefer advancing the master in little steps, just lemme know and we'll go that way. My initial idea was to resume working on usysconf in relive and eventually merge it into master. |
That's fine, these changes can wait 🙂
Personally, I would reserve the 'temporary master branch' (or 'long-lived feature branch') approach for when master is actively being developed and/or changes are likely to subtly break things. That doesn't seem the case here, so I would just advance master in little steps. |
@livingsilver94: I have rebased on the latest master. GLHF 😉 |
This PR adds configuration and a GitHub workflow action for golangci-lint. Trivially fixed linting issues have been fixed, and other linters disabled so they can be enabled with a little more care..