The part of the process that resets a ref to its previous commit if the SHA1 hasn't changed needs to be checked for interactions with ancestry. We probably want to avoid creating a new commit just because a branch was created, but otherwise we want to make sure that ancestry isn't dropped.
The part of the process that resets a ref to its previous commit if the SHA1 hasn't changed needs to be checked for interactions with ancestry. We probably want to avoid creating a new commit just because a branch was created, but otherwise we want to make sure that ancestry isn't dropped.