Apply clang-format style fixes to C++ source files#22
Closed
aurebidart wants to merge 8 commits into
Closed
Conversation
Co-authored-by: UE2 <unrealempowerment@gmail.com>
jonyMarino
force-pushed
the
main
branch
2 times, most recently
from
July 15, 2025 16:45
a41961c to
28b57f1
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
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.
About
This PR applies
clang-formatto all.cppand.hppfiles under version control to enforce a consistent code style across the C++ codebase. It follows the same rules defined by.clang-formatand the same filters defined in the CI workflow (excludingmavlinkcomandjson.hpp).No logic or functionality has been changed — this is a style-only commit.
How Has This Been Tested?
All changes were verified locally using:
The updated files now conform to the formatting rules, and the workflow
clang-format.ymlpasses successfully.Screenshots and videos (if appropriate):
N/A