cli: duplicate #187 commits stacked on test/argv-matrix-185 #219
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis#219
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The #187 work (
cli: publish the finite option vocabularies through clapandcli: snapshot every visible help page) exists a second time as unlabeled commits stacked ontest/argv-matrix-185(worktreeissue-185).Evidence:
git branch --contains 645708f5reportstest/argv-matrix-185andfix/schema-finite-strings-178; 645708f5 and its parent 915e5284 are a second copy of the same change based on105b0899(git merge-base 645708f5 origin/main=105b0899), i.e. the #187 work is stacked onto the #185 branch rather than onto a branch of its own.git -C .claude/worktrees/issue-185 status --shortadditionally showsM crates/felis-cli/src/tests.rswith 77 uncommitted insertions — the same file both #185 and #187 touch.Failure mechanism: a PR opened from
test/argv-matrix-185carries the #187 change as unrelated commits. Those commits are now onmain(d7b61a1b,1f8fa55c), so a rebase ontoorigin/mainwill either drop them or conflict oncli_output.rs/cli_sessions.rs/tests.rs, and the uncommitted 77 lines will be silently omitted from that PR.Correction: rebase
test/argv-matrix-185onto the currentorigin/mainso the two duplicate #187 commits fall away as already-applied, resolve or commit the pendingtests.rshunk deliberately, and verify the remaining diff contains only the #185 argv-matrix work before opening its PR.Deferred from #187 because it concerns another branch's hygiene, not #187's acceptance criteria.
Split from #187.
Closing: the duplicate commits were an artifact of a pipeline resume that replayed the already-merged #187 chain in a fresh worktree stacked on a stale branch, not a state of
mainor of any surviving branch. Those worktrees and local branches are deleted;maincarries #187 exactly once (915e5284, 645708f5 via PR 198).