Updated linter and .clang-format for ROS2 #412
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
bsutherland333
force-pushed
the
clang-tidy-linter-updates
branch
from
a0fd999 to
f3dd157
Compare
JMoore5353
approved these changes
Dec 15, 2023
bsutherland333
force-pushed
the
clang-tidy-linter-updates
branch
from
71952b4 to
b071e7c
Compare
|
F1 and F4 builds are currently broken, but are going to be removed shortly and replaced with a working build. |
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.
Some of the style guidelines have changed for ROS2, and since we want to keep a consistent style throughout ROSflight, I'm updating the firmware as well.
Lately, the existing format linter has also been disagreeing with the changes made by the fix_code_style.sh script, which has been pretty annoying. So this updates the action item to use a newer version as well, fixing the issue.