Introduce code formatting & linting #3
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
|
This PR contains the necessary files to run linting on your own machine (using clang-format and clang-tidy). It also includes the workflow for future PRs.
|
This is the first step towards consistent formatting rules in the codebase.
This ensures that the coding convention is enforced project-wide.
This workflow runs clang-format and clang-tidy on the whole repository and adds comments to PRs with formatting problems.
ros-dorian
force-pushed
the
feature/format-lint
branch
from
32bde7e to
1d90349
Compare
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 formatting and linting rules that need to be followed project-wide.
This makes use of the Clang tools clang-format and clang-tidy.