GitHub Community
Offer a checkbox for generate .git-blame-ignore-revs in rebase (or squash) merge
#16880
Replies: 1 comment
-
|
On the other hand, if that checkbox existed, I think beginners who don't really understand what Instead of a checkbox, I think that a PR that adds or modifies a |
Beta Was this translation helpful? Give feedback.
-
GitHub has a feature Rebase and merge and one for Squash and merge.
GitHub has a feature Ignore commits in the blame view which honors SHAs listed in
.git-blame-ignore-revs.I regularly create PRs to repositories that consist solely of spelling fixes. These commits would be great candidates for the
.git-blame-ignore-revsfile. But any repository that usesRebase and merge(orSquash and merge) makes it such that I can't actually offer a thing for.git-blame-ignore-revsbecause the commit SHA(s) to be added to the repository won't be known until after the rebase (or squash) and merge happens.Today, to address this, I basically have to make two PRs, one for the spelling fixes. Then after they're rebased (or squashed) and merged, I have to go back and create a new PR to ignore the SHA(s) created by that first PR. There's less incentive for me to do this step, and it looks like I'm gaming the system by creating additional commits/PRs (I really don't care, but people regularly accuse me of doing things like that).
The easiest (and safest) way for GitHub to help would be to offer a:
.git-blame-ignore-revsfor commit(s) in this PRBeta Was this translation helpful? Give feedback.
All reactions