Enforce compliance of clang-format style #375
Merged
Conversation
This file contains 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
diegoferigo
changed the title
traversaro
approved these changes
Jul 21, 2021
diegoferigo
force-pushed
the
feature/ci_clang_format
branch
from
a18d845 to
58adbaf
Compare
This was referenced Jul 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new workflow that uses diegoferigo/gh-action-clang-format to enforce on opened PRs the C++ style defined in the file
.clang-formatstored in the repository root.Note: the workflow filters only
*.cppand*.hfiles, therefore the vendored resources from upstream (that use*.hhand*.cc) are not affected.I plan on the long term to do something similar also for Python using black.