When a required check on a pull request shows “Expected” and “Waiting for status to be reported”, GitHub is waiting for a check with that exact name on the latest commit, and nothing is going to send it. The workflow never ran, or it ran under a different name. To unblock the merge, find the check name your branch rule requires, then either make a workflow report that name on this commit or remove it from the rule.
What does “Waiting for status to be reported” mean on GitHub?
Branch protection and rulesets can require named status checks to pass before a pull request merges. GitHub’s status check docs define Expected as a check run that is waiting for a status to be reported. Required checks must pass on the latest commit, and results from earlier commits don’t count. Every new push resets the wait, and a name no workflow produces waits forever. Our post on branch protection and required reviews covers the rest of those settings.
Required check name does not match the job name
The rule stores a name, and the check has to arrive under that name. With GitHub Actions the check is named after the job, and a job’s name key sets what GitHub shows in the UI. If the rule asks for build and no job reports under exactly that name, the requirement is never met. GitHub also warns that using the same job name in multiple workflows can give ambiguous results and block merges, so keep job names unique across workflows. Open the checks list on a recent pull request, copy the name exactly as it appears, and search for that name when you edit the rule.
Required check skipped by a paths filter or branch filter
If a workflow uses paths, branches or a commit message filter and the pull request doesn’t match, the workflow never starts. Per the troubleshooting guide for required checks, its checks then stay pending and block the merge. A docs-only change to a repository that requires a build job filtered to src/** will sit at Expected forever.
A job skipped by an if conditional reports Success and blocks nothing, which is the way out. Drop the workflow-level filter, let the workflow start on every pull request, and decide inside it whether the expensive job runs. Watch needs, though. A job skipped because a job it needs failed can let a merge through, and the same guide fixes that with always() on the dependent job.
Waiting for status in a merge queue: add merge_group
A merge queue runs the required checks again before it merges. The merge queue docs say you must trigger the workflow with the merge_group event, which is separate from pull_request and push. Without it, the check is never reported and the queued merge fails. Add it next to the existing trigger:
on:
pull_request:
merge_group:If queues are new to you, what a merge queue is explains what the queue tests and why.
Renamed job still required by the old name
Renaming a job changes the name it reports under. The rule still asks for the old one, which nothing produces any more, so every new pull request waits for it. Update the rule when you rename the job, ideally in the same change. Running the workflow by hand won’t clear it: checks from a workflow_dispatch run don’t show up on the pull request.
Matrix job names and required checks
A matrix job runs once for each combination of its variables, so it reports as several checks rather than under the plain job name. Requiring the bare job name then waits for a check no run reports. Require each matrix entry by the name shown in the checks list. If you gate on one final job that needs the matrix instead, give it always() as above, or a failed matrix entry skips it and the merge goes through.
How to unblock a pull request stuck at Expected
Compare the required names in the branch rule with the names on the checks list. If one is missing from the list, find out which of the causes above applies and fix the workflow or the rule. If the check was reported but came from a different app than the one the rule expects, GitHub blocks that too, so check the source app on the rule. If you changed the workflow, push a commit so it runs on the latest one. If you rely on auto-merge, it stays armed until that happens. One bad name in a rule can hold up several pull requests at once, and Pyor’s pull request lists have a Checks filter for rounding them up.
Frequently asked questions
What does Expected mean on a GitHub status check?
It means the check run is waiting for a status to be reported. GitHub knows the branch requires a check with that name, but nothing has reported it for the latest commit yet. If no workflow is going to run, it stays there and blocks the merge.
Can I merge a pull request while a required check says Expected?
Not through the normal merge button. The check has to pass on the latest commit first. An admin or a role with bypass permission may be able to merge anyway, but the real fix is to make the check report or to stop requiring a check that will never run.
Do skipped GitHub Actions jobs block required checks?
It depends on how they were skipped. A job skipped by an if conditional reports Success and does not block the merge. A whole workflow skipped by a paths, branches or commit message filter leaves its checks pending, and a pull request that requires them is blocked.