Add clang-format validation and apply fixes#16
Closed
aurebidart wants to merge 15 commits into
Closed
Conversation
Remove internal directory. Know it's called development Resolve merge corrections Co-authored-by: aurebidart <aure.bidart@gmail.com>
Add requirements.txt file sphinx rtd theme on requirements.txt file Co-authored-by: aurebidart <aure.bidart@gmail.com>
Co-authored-by: UE2 <unrealempowerment@gmail.com>
Fix README reference in Sphinx index to correctly include project ove…
- Added GitHub Actions workflow to validate clang-format - Applied clang-format-14 fixes to existing C++ code - Excluded mavlink and auto-generated files from validation
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
3 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.
About
This pull request introduces automated code style enforcement for C++ files in the repository using clang-format. A GitHub Actions workflow has been added to validate code formatting on every pull request and push, ensuring consistency across contributions. The workflow uses clang-format-14 and is configured to exclude mavlink and other auto-generated files from validation to prevent unnecessary errors and format changes.
Additionally, all existing C++ source files have been formatted according to the project's clang-format configuration. This helps standardize the codebase and makes future diffs easier to review.
How Has This Been Tested?