Why is my pull request "blocked"? Every reason GitHub stops a merge

A pull request has no conflicts, the code looks fine, and the merge button is grey with the words "Merging is blocked". In GitHub's API the same state is called blocked (the pull request field is mergeable_state, and the GraphQL field is mergeStateStatus). It means a rule on the target branch is not satisfied yet. The pull request itself is not broken.

The usual causes

How to find the actual reason

Related states you will see

Admins and bypass

Repository admins can often merge past a block unless "Do not allow bypassing the above settings" is on. A scheduled or automated merge made with a normal token or app follows the rules like everyone else, so if a human would be blocked, the tool is blocked too.

Why this matters for scheduled merges

A pull request that was ready when you scheduled it can be blocked by the time it is due: someone pushed a commit, an approval went stale, or a check is still running. A scheduler has to decide what to do. Merge Scheduler does not try to get around the block. It waits for checks that are still running, up to a limit you set, and skips the merge with the reason when the pull request stays blocked, so nothing merges at a time nobody planned.

Do this in Merge Scheduler: Schedule your first merge · Set up automatic revert for a failed deploy

Related: GitHub checks explained: check runs, commit statuses and required checks · "Expected: waiting for status to be reported": why a required check never starts · Why a scheduled merge should pin the commit you approved