Merge Queue running checks twice?

[dbartholomae]

Select Topic Area

Product Feedback

Body

It seems that merge queues load to running checks twice: Once on the PR, and then again on the merge queue. While this is needed when multiple PRs are batched together, it isn't needed when there is only on PR in the queue. Is there a way to automatically skip checks in that situation?

[vitorhugods]

Also found on the main Merge Queue feedback thread:

#46757 (comment)

This behaviour makes me think of the Merge Queue as a complicated automation on the "Update branch with target branch" button.
At a cost that it will take twice as long to check when it's already up-to-date.

[aldenquimby]

Also found here: #48792

[supotrois]

[purajit]

That's not what the issue here is - the issue is that when a PR is already up-to-date and at head of queue, there's nothing to be gained from re-running the checks while it's in the merge queue.

[gnwosu]

+1

[kiriti-kumo]

Is there any update on this issue? We waste a lot of Github Action minutes because of this duplicate checks even when the branch is up to date.

[sloanesturz]

Hi @willsmythe any update on this bugfix?

It's been almost a year since the Merge Queue went GA and this issue is still open and affecting lots and lots of Github users.

[BenEaston]

Hey @willsmythe any update on this? We'd love to speed things up with the merge queue!
Thanks