A pull request can pass every check and still stall after entering a GitHub merge queue. The queue checks the proposed combination of the target branch and queued changes. Its required status checks need results for that merge group, even if the original pull request already has green checks.


Find the check the queue is waiting for


Look at the rule for the target branch and write down the exact required check name. Then inspect the queue entry and the Actions runs associated with it. If a corresponding run never started, examine workflow events. If a run started but the check never appeared, compare its emitted job name and conditions against the requirement. If the check actually failed, start with that test’s error. Each state calls for a different correction.


Make required checks report on the merge group


For a required GitHub Actions workflow that currently triggers only on pull_request, add merge_group as an additional trigger while retaining the existing review trigger. Review job conditions for assumptions about the event. A test job might still be restricted to pull_request even though the workflow now starts in the queue. Keep operations that are meant exclusively for review or deployment under their own conditions.


For example, suppose the branch requires unit-tests. With only a pull_request trigger, a passing review run can leave the queue waiting for unit-tests. Add merge_group to the test workflow, then ensure the required job runs and reports under the same required check name for that event. You should be able to see a result tied to the queued group.


Verify a real queue run


Use an approved small change in a test repository or an ordinary low-risk pull request. Confirm the review run, then enqueue it and check that a new run starts for the merge group and reports the required result. Record the required name and workflow for the next person diagnosing it. This example is based on GitHub’s merge queue documentation.


Official reference