fix: muse branch --merged/--no-merged accept sha256: commit IDs
Previously crashed with a ValueError from validate_branch_name when the --merged/--no-merged argument was a commit ID rather than a branch name, since get_head_commit_id validates its input unconditionally as a branch name. Adds _resolve_into_tip() which recognizes a well-formed sha256: commit ID and uses it directly, falling back to the existing branch-name lookup otherwise.
Closes #21.
sha256:fcdc40f30b7dca01c5fb5e0a4e0665ef91185d23aaec91808101cc7845d6a475
sha
+18
~1
symbols
2 changed · 1126 in snapshot
files
sha256:9ed09ca6e27b3efa497c2ffc25ef84214b0814c809fb0190c866fcc136825a20
snapshot
+18
symbols added
~1
symbol modified
2
files changed
1126
files in snapshot
0
dead code introduced
Semantic Changes
19 symbols
+
test_merged_with_diverged_branch_by_commit_id
method
method test_merged_with_diverged_branch_by_commit_id L90–107
+
test_no_merged_accepts_sha256_commit_id
method
method test_no_merged_accepts_sha256_commit_id L66–77
~
run
Files Changed
+1
~1
1126 in snapshot
+1
~1
1126 in snapshot
← Older
Oldest on task/branch-merged-commit-id
All commits
Newer →
Latest on task/branch-merged-commit-id
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:fcdc40f30b7dca01c5fb5e0a4e0665ef91185d23aaec91808101cc7845d6a475 --body "your comment"
No comments yet. Be the first to start the discussion.