we have a long-lived development branch that is dearly paying the cost of non-grouped lands since graphite does not support more than one merge queue per repo. what can we do to avoid this? our preferred solution is to have the same merge queue policy (grouped PR merges) as our main queue

Hey Shaheen, Yes this is unfortunately a limitation today, one trunk / MQ per repo. We do have an experimental feature i can turn on for you that would specify which branch the trunk is (ie main) and any stacks not targeting that branch would use our normal stack merge. Not sure this helps in your case since it wouldnt allow for a second merge queue but happy to turn it on if youre interested. Just let me know the repo / trunk name~