git rebase: what can go wrong?

git rebase: what can go wrong?

Julia Evans

@b0rk the first thing I looked for when I got the idea of what this post was about was if you knew a solution to loss of gpg-signatures. It’s very much still something some people (at least me) care about a lot.

Another thing to add to the list is rebase merges can mess up the SHA of commits, making it impossible to add a .git-blame-ignore-revs in a PR containing the thing you wanna ignore.

@cafkafk ooh what is .git-blame-ignore-revs ? I've never heard of it
@b0rk It's where you put those super large trivial refactors that you don't want to clutter blame, e.g. when you do a treewide s/something/else/g