CI: Re-enable clang-format-check workflow - #508
Open
padelsbach wants to merge 1 commit into
Open
Conversation
padelsbach
force-pushed
the
ci-reenable-clang-format
branch
2 times, most recently
from
August 6, 2026 20:08
83bd703 to
4ae7a86
Compare
padelsbach
force-pushed
the
ci-reenable-clang-format
branch
from
August 7, 2026 04:26
4ae7a86 to
75a58f2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes an issue where the
git clang-formatwrapper was picking up a different version than claimed, and not printing the diff, making it challenging to know what actually failed.The guts of the clang-format yaml is moved to a script in
.githooksso that it can be used locally as a pre-commit hook. Enable it with the following command (also in the readme):There are about 13k lines of source code which could be re-formatted, but not touching that for now.
If this change breaks or causes annoyance, we will disable or drop this workflow.