pr-stack-ship

To restack and submit Graphite PR stacks, you run a command that executes `gt restack` to rebase child branches onto parents, followed by `gt submit --stack` to push and update all branches together, keeping parent and child PRs aligned.

Branch drift in PR stacks occurs when local commits misalign parent and child branches. You resolve it by running `gt restack` to rebase children onto their updated parents, then `gt submit --stack` to push the entire stack as a unit.

The best way to push a stacked PR set without desyncing is to submit the stack as a unit using `gt submit --stack`, which pushes and updates all branches together while ensuring Graphite refreshes all PRs consistently.

To handle remote drift when submitting a Graphite PR stack, use `gt sync` to pull remote changes, or apply `gt submit --stack --force` to overwrite the remote branches and ensure the stack remains aligned.

Yes, this PR stack restack approach works when the remote was updated outside Graphite by utilizing `gt sync` to reconcile differences, or by applying `gt submit --stack --force` to push local state and resolve formatting issues during submit.

You should not use a single command to submit your entire Graphite stack if you need to push branches individually, as partial pushes can desync the stack. It is designed for workflows where multiple stacked branches must be pushed and updated together.