Fix formatting #159
Closed
Fix formatting #159
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
|
Fixed in another 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.
Oops 🤦
Bisected to 682adf8
This also adds a
.git-blame-ignore-revsfile to ignore d43dab0 in GitHub's blame view. This is especially helpful for formatting commits that can introduce "clutter" to the blame that doesn't describe actual behavioral changes. More info: https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-viewJust a heads-up that the
.git-blame-ignore-revsfile won't work if this PR is squash or rebase merged, since that would create a new commit hash.Edit: now I see that "create merge commit" is disabled for this repo, so perhaps this
.git-blame-ignore-revsfile can go in a separate PR?