Submit stack

The multi-commit counterpart of the submit skill: each commit, prepared with commit-msg and usually tidied by squash, becomes one layer and one PR. Read the submit skill first; its rules for the description, the saved message, and outward-facing actions apply to every PR here unchanged. For gh stack itself, follow the gh-stack skill, including its non-interactive flags.

Takes an optional draft argument. gh stack submit opens drafts by default, so without draft pass --open.

Preconditions

• Git, or Sapling where git config has devroot.vcs=sapling, which follows its own section below.
• Stacked PRs are same-repository: origin has to be where the PRs open. In a fork layout, where upstream exists and the PRs belong upstream, stop and say so; offer submit for the bottom commit instead.
• Two or more commits over the base. One: use submit. When a stack is already checked out (gh stack view --json succeeds), every layer holds exactly one commit; a layer with several stops the run, with squash offered to fold it.
• Staged and working tree changes stay untouched: rewrite messages with --only, and stash nothing.

Steps