-
Notifications
You must be signed in to change notification settings - Fork 203
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
ci: minor polish, add codespell action, add clang permutation #206
Conversation
v2:
|
lsusb.c
Outdated
static const char * const encryption_type[] = { | ||
"UNSECURE", | ||
static const char *const encryption_type[] = { | ||
// clang-format off |
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.
That's not ok, sorry, if clang-format can't handle this, then don't use it.
It also doesn't have much to do with the codespell changes.
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.
Don't throw the baby out with the bathwater idiom comes to mind. No tool is perfect and the odd comment beats the very inconsistent code-base IMHO.
That said, I've dropped the ^^ hunk.
I took all but the first commit here. Can you split that up please? |
Make the code a bit more clean and consistent. Signed-off-by: Emil Velikov <[email protected]>
That's our defined style and that we've been using in the majority of the codebase. Disable clang-format on a couple of sections, where it gets a silly moment and insists on reformatting everything. Signed-off-by: Emil Velikov <[email protected]>
v2: - ignore NEWS, omit suppressions - split off style changes Signed-off-by: Emil Velikov <[email protected]>
Looks good, thanks for the changes! |
This PR cleans up a couple of minor ci bits and adds a few more actions.
Everything is run in parallel, so as far as turn around times are concerned there's no overhead.
While adding the codespell action, I've went through the whole repo and fixed a few issues. Although I'm not sure if we want the "UNSECURE" -> "INSECURE" one.
As a follow-up, I could update the existing run to use sanitizers so we get undefined behaviour, leaks, etc all flagged up as they appear... Assuming there is interest of course.