You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.
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 text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 text was updated successfully, but these errors were encountered: