fix(git): a start-cut branch is current, not zombie — ship commits on it#58
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
start cuts a named branch off origin/main carrying uncommitted work — zero unique commits, so git_branch_state called it zombie and ship recut ship/, stranding the named branch (2026-07-03 pile-up: resync dropped 4 zombie locals). The discriminator: a true merged leftover is BEHIND base; a start-cut home is AT base tip with a dirty tree — now classified current, in the one ladder, so every consumer (ship, repos --json, TUI queues) agrees. Two new git-flow.bats cases: the start-cut home targets itself; a dirty branch behind base is still recut. Closes task-ship-honors-the-start-cut-branch-one-branch-decision-in-the.