🧹 Standard Codebase Format #526
Draft
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
jameskr97
force-pushed
the
feature/clang-format
branch
5 times, most recently
from
15286a2
to
d222784
Compare
jameskr97
force-pushed
the
feature/clang-format
branch
from
9380997
to
912d7c6
Compare
jameskr97
changed the title
jameskr97
force-pushed
the
feature/clang-format
branch
from
912d7c6
to
636f1a2
Compare
|
The above force-push is a rebase on develop. |
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.
clang-format through CI
This PR will introduce a consistent format across the codebase.
PR Changes
.clang-formathas reached an agreed-upon format among etterna developers and contributorsformattarget has been added to CMake to allow for easy updates of code format.editorconfigupdated to match.clang-formatconfig