chore: ignore pure-move commits in git blame - #58
Merged
Conversation
The module split moved ~2000 lines, so blame pointed at that commit for a large part of src/. Recording it here sends blame back to the change that actually wrote each line. Future move-only commits go in the same list.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The module split (#57) moved about 2000 lines, so
git blamenow points at that commit for a large part ofsrc/. This records it as a move-only revision, which GitHub and local git both honour, sending blame back to the change that actually wrote each line.The SHA could not be included in #57 itself: squash-merging mints a new commit, so the value only exists once that PR has landed.
Future move-only commits go in the same list. Locally:
git config blame.ignoreRevsFile .git-blame-ignore-revs.