Clang format everything #2605
Merged
Clang format everything #2605
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 was breaking clang-format
Requires clang-format 15+, CI only has 14
|
Can we use clang 15 in CI? We could use e.g. the fedora images, they come with clang 15 ... |
bendudson
approved these changes
Nov 16, 2022
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.
Applies clang-format to the entire repo, including the new option "insert braces" (this requires clang-format 15, CI only has 14, so it's currently disabled in the config file)
.git-blame-ignore-revs contains the commit hashes of the two main commits that touch everything. If you add
to your
~/.gitconfig, then these commits should be ignored when runninggit blame