"Expected: waiting for status to be reported": why a required check never starts
A pull request is blocked and one required check sits there as "Expected", with the words "Waiting for status to be reported". Nothing is running and nothing will. GitHub is waiting for a check with that exact name, and no one is sending it.
Why it happens
- The workflow was skipped by a path filter, a branch filter or paths-ignore. When a whole workflow does not run, its checks stay pending and the required check never reports.
- The commit message contains a skip marker such as [skip ci], so no workflow started.
- The job or workflow was renamed. The rule still asks for the old name.
- A matrix changed. The job names it produces are different from the names the rule requires.
- The workflow does not trigger for pull requests into that branch, for example it only runs on push.
- Two workflows produce checks with the same name, and GitHub cannot tell which one the rule means.
- The workflow file has a syntax error, so it never started.
How to fix it
- Open the Actions tab and look for a run for the head commit. No run means a trigger or filter problem. A run with an error means a workflow problem.
- Make required workflows always run, and move the "only when these files changed" decision inside the workflow, as a condition on the job. A job skipped by a condition reports as success, so the required check is satisfied.
- Or add one final job that summarises the others and mark only that job as required. Then renaming or changing a matrix does not break the rule.
- After renaming a check, update the required checks list in the branch protection rule.
Why it is worse with scheduled merges
A pull request that waits forever for a check that will never come does not fix itself. A scheduled merge that keeps waiting would hold the branch. Merge Scheduler waits only up to the limit you set (60 minutes by default). After that it skips the merge and tells you which checks were still pending, so you can fix the rule and reschedule.
Do this in Merge Scheduler: Schedule your first merge
Related: Why is my pull request "blocked"? Every reason GitHub stops a merge · GitHub checks explained: check runs, commit statuses and required checks · Why a merged pull request didn't start your deploy workflow