fix: fall back to DB ancestry check when mpack-only fast-forward walk fails
_is_fast_forward walks only commits present in the mpack. When new commits build on top of commits already on the remote (those are in 'have' and absent from the mpack), the walk hits a parent that is not in the mpack and stops prematurely, returning False even though the push is a valid fast-forward.
Fix: after the mpack walk returns False, fall back to _is_ancestor_db which queries MusehubCommitGraph to verify that current_head is a true ancestor of the incoming tip. Only raise NonFastForwardError if both checks fail.
sha256:7d6dd8f4a89e2d1fef2d84f6e65feaff51385d382f466766b7f690a22ec18e32
sha
+1
~15
symbols
972 changed · 972 in snapshot
files
sha256:230cbe6290c70b754c38da63346fcaefba6096729a401715048a22295bf2e1b7
snapshot
+1
symbol added
~15
symbols modified
972
files changed
972
files in snapshot
0
dead code introduced
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:7d6dd8f4a89e2d1fef2d84f6e65feaff51385d382f466766b7f690a22ec18e32 --body "your comment"
No comments yet. Be the first to start the discussion.