For the best experience, we recommend merging a stack of pull requests through Graphite.
Merging with the Graphite app saves a substantial amount of time. However, if you'd like to manually merge your PRs, merge the PRs in the stack one at a time:
Merge the bottom PR of your stack into your trunk on the Graphite app (or through GitHub).
gt syncfrom any branch of your stack to pull
trunkto local, delete the merged branch, and restack the rest of your stack on
From any branch in your stack, run
gt submitto force push the restacked branches so the new bottom of your stack can be merged into
Repeat until you've landed all of the branches in your stack.
We recommend always merging from the bottom of the stack. While there are other techniques, we've found that this is the most intuitive and safest model for our users.
Merging in reverse order from the middle or top of the stack and collapsing all of the PRs into one is the fastest way to merge an entire stack, but there are a number of pitfalls for users—namely around syncing this merged state locally (to continue developing on any upstack PRs) or undoing these changes if a user decides not to merge a PR. This may lead to perilous situations where users have felt like they've lost code or can't re-create their previous state.
While certainly not impossible, it's also harder to re-derive the original stack of PRs when looking at the
To help prevent accidental mid-stack merges, Graphite creates an optional status check on GitHub for upstack PRs. This status check fails for all upstack PRs, and passes for all base PRs. It does not run on non-Graphite PRs.
Since it's optional by default, you can still merge mid-stack if needed. Teams can make this check required in order to fully prevent merging PRs in a stack out of order.
To disable this feature for your GitHub org:
Open the Graphite web app's settings page
Select the "Organization" page
Mergeability status checks on GitHubsetting