Mehul Chokshi
10/22/2025, 6:36 AMPylon
10/22/2025, 6:36 AMPylon
10/22/2025, 12:15 PMLuke Pighetti
10/22/2025, 8:34 PMPylon
10/22/2025, 8:37 PMLuke Pighetti
10/22/2025, 8:46 PMPylon
10/22/2025, 9:41 PMMehul Chokshi
10/23/2025, 2:40 AMThe Graphite Merge Queue is stack-aware, providing opportunities for faster concurrent/batched merges and optimizing the order in which PRs are merged. So if the stack is added to the queue together, the merge queue can process and validate the entire stack in parallel. No need for CI to run again since we have already validated the CI against that exact change (this is also known as fast-forward merge, as described below).Pylon
10/23/2025, 1:07 PMWill the stack be rebased automatically between merges? will I be manually rebasing all the time?
Automatic rebasing will be attempted so long as you click
merge from the Graphite app. This feature does not work when merging from GitHub.
With the regular Stack Merge, It is still possible to manually merge an individual PR or stack of PRs in GitHub, however this will require manually syncing and submitting after each PR merges to ensure the stack is rebased and Graphite is aware of the new state. More information on manual merging here.
If I use github merge queue I mostly lose out on the below right
Yes, unlike Graphite’s merge queue, external merge queues don’t use stack context to optimize merges, so you won’t benefit from the same performance boosts and guarantees available with the Graphite merge queue. More information about the limitations here.