feat(stage): muse code add auto-resolves conflict paths (git-idiomatic)
In git, `git add <file>` after editing a conflict is the resolution signal — no separate step. muse code add now does the same: any staged file that appears in MERGE_STATE conflict_paths is removed from that list automatically, so `muse commit` can proceed without an explicit `muse resolve`.
muse resolve remains available as an explicit escape hatch for --all, symbol-level resolution, and agent workflows.
sha256:45bf7b7727da29ab5c67698be748c0ab8300ce0b8523868994a4b06e54a54b4e
sha
+30
~1
symbols
sha256:6638c43f9db336c22e0a90e6f8973fc2905c02bd97a75a6fb381042022fce908
snapshot
+30
symbols added
~1
symbol modified
0
dead code introduced
Semantic Changes
31 symbols
+
test_code_add_dot_clears_all_conflict_files
method
method test_code_add_dot_clears_all_conflict_files L225–258
+
test_no_merge_in_progress_code_add_is_unaffected
method
method test_no_merge_in_progress_code_add_is_unaffected L260–271
+
test_staging_conflict_file_allows_commit
method
method test_staging_conflict_file_allows_commit L142–158
+
test_staging_conflict_file_removes_it_from_conflict_paths
method
method test_staging_conflict_file_removes_it_from_conflict_paths L128–140
+
test_staging_conflict_file_sets_ready_to_commit_when_last_conflict
method
method test_staging_conflict_file_sets_ready_to_commit_when_last_conflict L160–174
+
test_staging_non_conflict_file_does_not_touch_merge_state
method
method test_staging_non_conflict_file_does_not_touch_merge_state L176–188
+
test_staging_one_of_two_conflict_files_leaves_other_unresolved
method
method test_staging_one_of_two_conflict_files_leaves_other_unresolved L190–223
~
run_add
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:45bf7b7727da29ab5c67698be748c0ab8300ce0b8523868994a4b06e54a54b4e --body "your comment"
No comments yet. Be the first to start the discussion.