PR repeatedly removed from merge queue due to failed status checks #168145

liblit · 2025-07-30T17:05:01Z

liblit
Jul 30, 2025

Select Topic Area

Bug

Body

Description

The WALA Project recently enabled the merge queue. However, we find that approved, checked pull requests are repeatedly removed from the merge queue "due to failed status checks". Re-submitting the same PR multiple times does not resolve the problem. It is unclear exactly which status checks are failing or what, if anything, the project's maintainers can do to fix them.

Is this a merge queue bug? Have we made some mistake in how we configured our CI infrastructure? Any help would be greatly appreciated.

Reproduction Steps

We are currently seeing this problem with this pull request. The changes have received the required approvals from human reviewers, and all automated checks have passed. But I have added this pull request to the merge queue three times, and each time the github-merge-queue bot has removed it:

github-merge-queue bot removed this pull request from the merge queue due to failed status checks

We can reproduce the problem by re-submitting this PR to the merge queue.

Not every PR is affected in this way; the merge queue has worked as intended for some PRs, but gotten stuck in this way for others. I don't know what distinguishes the PRs that the merge queue accepts from those that are repeatedly removed. Once we have a single removal, though, that state seems persistent for a given PR: we can re-queue an affected PR as many times as we want, but it will always be removed again.

Logs

If I click "View details" for one of the "removed…due to failed status checks" messages, I see that "11 of 19 checks passed". The list of checks shows nearly every check twice: once successfully completed and once canceled. If I click on "Details" for one of the canceled checks, then I see a CI job page like this one. That page's Annotations list reports the same error twice:

Canceling since a higher priority waiting request for Continuous integration-gh-readonly-queue/master/pr-1593-5c412c866e320f3497cde748d04264ad09f4db90-c38b703fe9eaabab593f9a7c00b53276e141c1cc exists

I find this error confusing given that the project's merge queue is currently empty. This project's actions list also shows nothing going on.

Answered by liblit

Jul 31, 2025

Problem diagnosed, explained, and solved by Arthur from GitHub Support:

Checking out the example you shared, two runs of the same workflow are getting triggered when adding the PR to the merge queue - one run on merge_group, and then one run on the push to the merge queue branch gh-readonly-queue/**.

Both of these runs resolve the same concurrency group value, causing one of them to be cancelled due to cancel-in-progress being true.

To resolve this, you can edit your workflow file to specify not triggering on pushes to merge queue branches to reduce the duplicate runs here.
push:
  branches-ignore:
    - 'dependabot/**'
    - 'gh-readonly-queue/**'

Arthur's suggested fix worked perfectl…

View full answer

liblit · 2025-07-31T20:16:54Z

liblit
Jul 31, 2025
Author

Problem diagnosed, explained, and solved by Arthur from GitHub Support:

Checking out the example you shared, two runs of the same workflow are getting triggered when adding the PR to the merge queue - one run on merge_group, and then one run on the push to the merge queue branch gh-readonly-queue/**.

Both of these runs resolve the same concurrency group value, causing one of them to be cancelled due to cancel-in-progress being true.

To resolve this, you can edit your workflow file to specify not triggering on pushes to merge queue branches to reduce the duplicate runs here.
push:
  branches-ignore:
    - 'dependabot/**'
    - 'gh-readonly-queue/**'

Arthur's suggested fix worked perfectly. Thanks, Arthur! 👏

0 replies

2025-07-30T17:05:29Z

github-actions[bot]
bot Jul 30, 2025

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

Your input will be carefully reviewed and cataloged by members of our product teams.
- Due to the high volume of submissions, we may not always be able to provide individual responses.
- Rest assured, your feedback will help chart our course for product improvements.
Other users may engage with your post, sharing their own perspectives or experiences.
GitHub staff may reach out for further clarification or insight.
- We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

Upvote and comment on other user feedback Discussions that resonate with you.
Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

PR repeatedly removed from merge queue due to failed status checks #168145

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

GitHub Community

PR repeatedly removed from merge queue due to failed status checks #168145

Uh oh!

Uh oh!

liblit Jul 30, 2025

Select Topic Area

Body

Description

Reproduction Steps

Logs

Replies: 2 comments

Uh oh!

liblit Jul 31, 2025 Author

Uh oh!

github-actions[bot] bot Jul 30, 2025

liblit
Jul 30, 2025

liblit
Jul 31, 2025
Author

github-actions[bot]
bot Jul 30, 2025