fix(push): force push uses empty have-set — never exclude objects on force
When --force is used the server's existing branch heads cannot be trusted as object-coverage anchors. The remote may have objects absent from its DB (DB migration, partial prior push, diverged history).
Walking with those anchors excluded exactly N objects the server lacked, producing a guaranteed 422 integrity-check failure. With have=[], the walk sends all objects from root, ensuring the server gets everything.
sha256:c27dd183c52a1ad3d93f5e8d03a90ac49ba8d203d2aa21b6d0efe2a8a044aaf7
sha
sha256:49a6c927a59887b5909423b15b9ca3f04e4407fc24366d23b7ed9c270f06a9b5
snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:c27dd183c52a1ad3d93f5e8d03a90ac49ba8d203d2aa21b6d0efe2a8a044aaf7 --body "your comment"
No comments yet. Be the first to start the discussion.