Fix formatting error because of missing backtick #338
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
|
I doubt that the failing clang-format check has anything to do with the added backtick. Not sure what's going on there, maybe someone with knowledge about the CI-pipeline can say? |
|
Looks like the CI warning was introduced by my last PR; #336 was merged with clang-format still failing, oops. Should be ignorable for purposes of this PR. |
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.
I noticed that the formatting of the last part of the docs for i2c2midi-commands is screwed up (from the entry for "I2M.C.ROT x y" onwards) because of a missing backtick. This PR adds that missing backtick to unscrew said formatting.