We've recently enabled the graphite merge queue. W...
# how-do-i
a
We've recently enabled the graphite merge queue. Why does graphite sometimes merge from a
gtmq_**
branch into
main
, and sometimes from a
gtmq_**
branch into a different
gtmq_**
branch? In the latter scenario, some of our CI (including our required check, merge_gatekeeper) doesn't run because it's only configured to run on merges to main. This is causing the PRs in the merge queue to time out. Is there a graphite merge queue setting that is causing this?
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
a
Update: Pretty sure this was from having parallel CI set to > 1. We didn't actually need that, so set it to 1 to work around
p
hey Anna, yeah the creation of branches with the
gtmq_
prefix would be expected behavior for the parallel CI feature
👍 1