Skip to content

feat(nav): interactive ez up/down when the stack forks#21

Merged
rohoswagger merged 1 commit into
mainfrom
feat/up-down-navigate
May 9, 2026
Merged

feat(nav): interactive ez up/down when the stack forks#21
rohoswagger merged 1 commit into
mainfrom
feat/up-down-navigate

Conversation

@rohoswagger
Copy link
Copy Markdown
Owner

Summary

When several branches stack on the same parent (e.g. multiple roots off main), ez up used to always pick the first sorted child name. That made navigation feel broken.

Changes

  • TTY: If there are multiple child branches, ez up opens a dialoguer picker (same family as ez switch), with optional [wt: …] suffix for linked worktrees and PR badges when metadata has a PR number.
  • Non-interactive: Exit 5 with an error that lists child branches and tells the caller to run ez up <branch> or ez up <pr-number> when those children are direct children of the current branch.
  • ez down: Optional parent argument (ez down main) so scripts can assert the stack parent matches before switching.
  • ez bottom from trunk: Uses the same disambiguation as ez up when there are multiple stack roots off trunk (instead of silently picking the first sorted name).

Agent workflow

ez up testy-2
# or
ez up 42  # PR number must belong to a direct child of the current branch

Made with Cursor

- TTY: dialoguer picker when multiple child branches share a parent
- Non-TTY: list children and require ez up <branch> or PR number
- ez down optional parent arg for script assertions
- ez bottom from trunk uses same disambiguation as ez up

Co-authored-by: Cursor <cursoragent@cursor.com>
@rohoswagger rohoswagger linked an issue May 9, 2026 that may be closed by this pull request
@rohoswagger rohoswagger merged commit 00ae816 into main May 9, 2026
4 checks passed
@rohoswagger rohoswagger deleted the feat/up-down-navigate branch May 9, 2026 00:13
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.

Unable to navigate in the stack tree

1 participant