How does git-rebase recognize “aliased” commits?
问题 I'm trying to better understand the magic behind git-rebase. I was very pleasantly surprised today by the following behavior, which I didn't expect. TLDR: I rebased a shared branch, causing all commit sha1s to change. Despite this, a derived branch was able to accurately identify that its original commits were "aliased" into new commits with different sha1s. The rebase didn't create any mess at all. Details Take a master branch: M1 Branch it off into branch-X, with some additional commits