Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

fix(cmd): defer submit push until PR intent is known

Submit used to force-push every stack branch before the PR phase, so
branches were published even when the user skipped opening a PR.

Plan each branch first (GitHub adopt check, prompts, --update-only),
then push only branches that will get PR work or must exist on the
remote as a base for a descendant PR. PR execution reuses the plan.

Add a unit test for ancestor push propagation on skip.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>

`cascade` is still retained as an alias of `restack`.

**WARNING**: This may invalidate in-progress cascade operations if you happen to upgrade `gh-stack` in the middle of one. Don't do that.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

BREAKING CHANGE: Some flags have changed. `restack`: `--only` is now `-c, --current`; `submit`: `--current-only` is now `-c, --current`, `--update-only` is now `-u, --update`, `--push-only` is now `-s, --skip-prs`, removed `-w` shorthand from `--web`.

Other options have had shorthands added; see [README.md](https://github.com/boneskull/gh-stack/blob/main/README.md) for details.

…unk (#100)

* fix(submit): only prompt to publish draft when base transitions to trunk

Resolves #95. Previously, `gh stack submit` would prompt to publish a
draft PR every time it ran, as long as the PR was a draft and targeted
trunk. This got annoying fast.

The fix adds a `stackPRBase` key to `.git/config` (per branch) that
persists the last-known remote base after each successful submit run.
The publish prompt now fires only when the stored base differs from
trunk — i.e., the PR's base is genuinely moving to trunk for the first
time since the last submit.

Cleanup is consistent: `unlink`, `orphan`, and sync's merged-branch
handlers all clear `stackPRBase` alongside the other per-branch config
keys. Sync's retarget-to-trunk path also persists the new base so
subsequent submit runs don't re-prompt.

* fix(submit): check trunk transition before persisting new PR base

The `prActionUpdate` path in `executePRDecisions` was calling
`SetPRBase` before `maybeMarkPRReady`, which meant
`isTransitionToTrunk` always read the value we had just written
(trunk) and returned false. The publish-draft prompt was therefore
silently suppressed for all existing PRs transitioning to trunk.

Fix: call `maybeMarkPRReady` first, then persist the new base.
While here, move `GenerateAndPostStackComment` inside the success
branch so it doesn't run when `UpdatePRBase` fails.

Add `TestIsTransitionToTrunkOrderingInvariant` to document and
guard the required call order.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>