Problem
Without --from, ez create always stacks the new branch on top of the current branch. Many workflows use a non-trunk integration branch (e.g. dev, staging, release/next) as the default base for new work. There is no way to configure a default parent.
Current behavior
ez create foo stacks on whatever branch is checked out
ez create foo --from main works but must be specified every time
- No config for "default base branch" distinct from trunk
Proposed solution
- Add
default_from (or default_parent) to .git/ez/stack.json
- When
--from is not specified and the current branch is trunk, use default_from if set
ez config set default-from <branch> to configure
- Falls back to current behavior (stack on current branch) when unset
Use cases
- Teams that develop against
dev and only merge dev → main for releases
- Repos with multiple long-lived integration branches
- Avoiding accidental deep stacking when user forgets
--from
Problem
Without
--from,ez createalways stacks the new branch on top of the current branch. Many workflows use a non-trunk integration branch (e.g.dev,staging,release/next) as the default base for new work. There is no way to configure a default parent.Current behavior
ez create foostacks on whatever branch is checked outez create foo --from mainworks but must be specified every timeProposed solution
default_from(ordefault_parent) to.git/ez/stack.json--fromis not specified and the current branch is trunk, usedefault_fromif setez config set default-from <branch>to configureUse cases
devand only mergedev→mainfor releases--from