Correct formatting of C code #843
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
Apply the coding standards to the C code from eclipse-cdt#840
|
The binaries were correctly built, but I had forgotten we never got code formatting for C code checks running on GH Actions, so #840 introduced a build failure when running full build on Jenkins. |
|
This build properly on Jenkins where the code cleanliness ran https://ci.eclipse.org/cdt/job/cdt-jonahgraham-fork/job/correct-formatting/ |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
jonahgraham
added a commit
to jonahgraham/cdt
that referenced
this pull request
Jun 28, 2024
Apply the coding standards to the C code from eclipse-cdt#840 (cherry picked from commit 24d9bd1)
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.
Apply the coding standards to the C code from #840