Skip to content

fix(canary): delete the non-current split layer with plain run - #158

Merged
rohoswagger merged 1 commit into
mainfrom
fix/canary-split-cleanup
Aug 12, 2026
Merged

fix(canary): delete the non-current split layer with plain run#158
rohoswagger merged 1 commit into
mainfrom
fix/canary-split-cleanup

Conversation

@rohoswagger

Copy link
Copy Markdown
Owner

The v0.3.4 release failed at the canary gate — on a bug in the canary script I added in #156, not in ez.

✓ Deleted branch `ez-canary/.../split-src-1`
github-canary: ez delete did not return a worktree path:
##[error]Process completed with exit code 1

navigate_to_output expects ez delete to print a worktree path to cd into, which only happens when you delete the branch you are currently standing on. After ez split, the current branch is the top layer (split-src), so deleting the lower layer split-src-1 prints nothing and the helper treated that as a failure.

ez split itself ran correctly in that canary run — create, two commits, --dry-run, split, and log all passed against real GitHub. Only the cleanup line was wrong.

Uses plain run for the non-current branch, with a comment explaining the distinction so the next person doesn't reach for navigate_to_output again.

…th plain run

`navigate_to_output` requires `ez delete` to print a worktree path to cd into,
which only happens when deleting the branch you are standing on. After
`ez split`, the current branch is the top layer (`split-src`), so deleting the
lower layer `split-src-1` prints nothing and the helper failed the canary —
blocking the v0.3.4 release on a bug in the canary script, not in ez.

The split itself ran correctly in that canary; only the cleanup was wrong.
@rohoswagger
rohoswagger merged commit 8e54c2d into main Aug 12, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant