add a .clang-format file #9154
Merged
add a .clang-format file #9154
Conversation
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
Member
Author
|
In VC @thebentern pointed out this is a big merge conflicts risk. I agree, however it is easy to fix. |
thebentern
approved these changes
Jan 2, 2026
Jorropo
force-pushed
the
clang-format
branch
3 times, most recently
from
53547e1 to
d2e2c28
Compare
The previous setup would be extremely lenient. AFAIK would basically only enforce tabulation more or less. Add a .clang-format file, the point is you can't accidently have whitespace changes. See meshtastic#9116 for what sitatuation we are in before this patch. The point is there is a single valid way to format the file, and running trunk fmt -a will bring you to it.
NomDeTom
pushed a commit
to NomDeTom/MeshtasticFirmware
that referenced
this pull request
Jan 4, 2026
Jorropo
added a commit
to Jorropo/firmware
that referenced
this pull request
Jan 4, 2026
I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into master. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331.
Jorropo
added a commit
to Jorropo/firmware
that referenced
this pull request
Jan 4, 2026
I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331.
thebentern
pushed a commit
that referenced
this pull request
Jan 4, 2026
I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The previous setup would be extremely lenient.
AFAIK would basically only enforce tabulation more or less.
Add a .clang-format file, the point is you can't accidently have whitespace changes. See #9116 for what sitatuation we are in before this patch.
The point is there is a single valid way to format the file, and running trunk fmt -a will bring you to it.