We're considering using the merge queue—does it su...
# how-do-i
m
We're considering using the merge queue—does it support skipping the queue if a PR is already up to date and rebased? I.e., if you create a branch out of main and all tests have already succeeded on the PR, is it able to skip re-running tests on a new branch before merging? This is a limitation with the GitHub merge queue that has stopped us from using it.
n
Yes it should!
(cc @David Bradford in case you want to add any other context)
m
Nice! I'll give it a try then.
j
I think you may need to ensure that the fast-forward option is selected in order to achieve this behavior
I also defer to Dave on these things though 🙂
d
Yes, you should get this behavior in the merge queue if you have fast-forward enabled.
m
Thank you, I'll make sure that's enabled
Took a minute but it looks like it worked, nice! Thanks.
🔥 1
Is there any way to add a PR to the merge queue before its tests complete? If it's going to have to rebase a PR anyway it seems like that would save some time
d
Right now there is not. I generally recommend against adding anything to the merge queue that has not already passed tests. It is better to hit any failures before you add PRs to the merge queue. Since failures in the merge queue not only impact (slow down) the author of the PR, but everyone else who has PRs in the merge queue.
m
That's fair, thanks!
Is there a trick to activating the "queue with label" feature? I've added it to the
Add to merge queue via label
settings but it doesn't seem to be doing anything when I add the label
Hm, when I then went and clicked in the Graphite app instead it commented that it detected the label:
I added the label 5 minutes before
d
We have been seeing some instability with the github API over the last few hours, which could explain why detecting the label was delayed.
👍 1