-
Notifications
You must be signed in to change notification settings - Fork 4
meta: Update CI and follow linter suggestions #21
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
base: master
Are you sure you want to change the base?
Conversation
8c7f7f4 to
8986a5c
Compare
6b8fdbb to
f1bb981
Compare
I have no idea if that's how to handle errors in goroutines and deferred function calls. Please review properly.
f1bb981 to
e0c1690
Compare
|
Sooooo i spent a few hours playing robot with my keyboard and monkeytyping stuff to get the CI working. I'm disabled a few imho useless lints, and there's just 2 left that don't pass and i think are important and require some level of review:
Otherwise on this branch golangci-lint should run without simply comparing errors with the previous commit which is a terrible way to accumulate tech debt and let it fall on the first person submitting a PR. Feel free to review. In particular, this commit deserves special attention: d47a7dc Because i have no idea what i'm doing in there i'm merely working around the linter errors and i don't know what's the idiomatic way to handle defer/goroutine errors in golang. |
I noticed CI was failing on #20 but i could not reproduce because the version of
golangci-lintis so old… so i updated to latest github actions release, and tested with the latest golangci-lint release.I had to remove some linters i have no idea what they do but they don't exist anymore. Some migration stuff was documented here but not everything because we were so old (our config wasn't even versioned so the migrate subcommand failed to validate).
Anyway i'm not sure it'll pass yet so let's pray to the CI gods :)