test(commit): Phase 5 — stage preserved on branch-conflict failure
Regression suite confirming that clear_stage is never called when write_branch_ref fails with RefConflictError.
Phase 1's CAS fix implicitly ensured this (SystemExit before clear_stage), but without an explicit test the invariant had no coverage. Three tests: - staged files still appear in status after conflict - staged file content unchanged after failed commit - multiple staged files all survive
sha256:32fb73a6604624a3a0bb2a08b53306bf39844f8814733cbb51798fe368ca53f7
sha
+14
symbols
sha256:dc1db1bae795cb64ea6dcd1eb713af91b6a1fb7f3cabdf39d4ad769127a11f29
snapshot
+14
symbols added
0
dead code introduced
Semantic Changes
14 symbols
+
test_multiple_staged_files_all_preserved
method
method test_multiple_staged_files_all_preserved L104–123
+
test_staged_file_content_intact_after_conflict
method
method test_staged_file_content_intact_after_conflict L86–102
+
test_staged_files_still_staged_after_conflict
method
method test_staged_files_still_staged_after_conflict L55–84
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:32fb73a6604624a3a0bb2a08b53306bf39844f8814733cbb51798fe368ca53f7 --body "your comment"
No comments yet. Be the first to start the discussion.