Skipping checks with merge queue if the branch is already up to date

[pezholio]

Select Topic Area

Question

Body

Hi,

We've recently started using Merge Queues, and they're looking like a good solution for our velocity, especially on busy repos. However, it is slowing us down a bit when a branch is already up to date with main, where our checks have to get run again in the merge queue, meaning they're running twice before a branch gets merged. Is there a way to skip these checks (through some github actions magic or similar) if our branch is already up to date?

[aldenquimby]

Noting this is the same as #43988 and is also on the main feedback thread here

[sloanesturz]

Hi @willsmythe! Any update on this issue? This appears to be affecting many customer's ability to adopt the Merge Queue.

Thanks!

[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.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[paulbalaji]

If you fix this then we wouldn't be complaining. How is it September 2024 and this extremely basic feature isn't in GH directly?