Tim Boucher
06/30/2025, 7:07 PMmain). I had added our merge queue label before the build finished and thought the queue would merge it quickly. Instead Graphite pushed a new commit which triggered a new build, delaying the final merge.
Not a big deal in this instance but I’d like to understand why because that’s wastefulPylon
06/30/2025, 7:07 PMgt feedback --with-debug-context <any message>Tim Boucher
06/30/2025, 7:07 PMTim Boucher
06/30/2025, 7:13 PMTim Boucher
06/30/2025, 7:16 PMTim Boucher
06/30/2025, 7:16 PMPylon
06/30/2025, 8:10 PMTim Boucher
07/16/2025, 7:28 PMTim Boucher
09/25/2025, 5:56 PMTim Boucher
09/25/2025, 5:56 PMTim Boucher
09/25/2025, 6:18 PMPylon
09/26/2025, 4:10 PMTim Boucher
09/26/2025, 5:54 PMmain, with all necessary approvals and builds had passed. I could have clicked “Squash and merge” on GitHub.
Instead, I went to Graphite, and clicked “merge stack”. I had three branches at the time and they were all approved.
We use the Graphite merge queue.
Once I did that, I expected Graphite to just merge the branch immediately since it was up-to-date with main and all green. Instead, Graphite pushed a new version to the branch, which triggered a new build to start.
That build unfortunately failed (flaky test), which kicked the whole stack out of the Graphite merge queue.
So I had to restart the builds, and add the stack to the Graphite merge queue again.Tim Boucher
09/26/2025, 5:54 PMTim Boucher
09/26/2025, 5:56 PM