Skip to content

merge blockers

Why a GitHub pull request sits on "Checking for ability to merge automatically", and how to get it moving

Othman Shareef · November 22, 2026 · 5 min read


“Checking for ability to merge automatically” means GitHub is still building a test merge of your branch into the base to see whether it conflicts. It usually clears in seconds. If it hangs, reload the page, since viewing the pull request is one of the things that makes GitHub run the check. If it’s still there minutes later, look at the Pull Requests component on githubstatus.com. During an incident nothing on your side will fix it.

What does “Checking for ability to merge automatically” mean?

Per GitHub’s REST docs for pull requests, when you get, create, or edit a pull request, GitHub creates a merge commit to test whether it can be merged automatically into the base branch. That test commit is not added to either branch. Until the job finishes, the mergeable field is null, and the docs say GitHub “has started a background job to compute the mergeability.” The banner on the pull request page is that same wait.

The GraphQL reference names three states: MERGEABLE, CONFLICTING, and UNKNOWN, which it describes as mergeability that is still being calculated. The check is only about conflicts. Reviews, required checks, and rules block the merge separately.

Why is my pull request stuck checking for ability to merge?

  • The job has not run yet. GitHub builds test merges on demand. Its Git database guide says a test merge commit is created when you view the pull request in the UI and the Merge button is displayed, and that without such a request the merge refs fall out of date until the next time someone views the pull request.
  • Something just changed. A push to your branch or new commits on the base make the last test merge stale, so GitHub computes it again.
  • GitHub is having an incident. If every pull request you open shows the message, the problem is probably on GitHub’s side.

How do I fix “Checking for ability to merge automatically”?

  1. Wait a few seconds and reload the pull request page.
  2. Ask the API directly. gh api repos/OWNER/REPO/pulls/NUMBER --jq .mergeable requests the pull request, which is one of the actions that triggers the test merge. If it prints null, wait and run it again, as the docs recommend.
  3. Edit the pull request, for example its title. Editing is also listed as a trigger for the test merge commit.
  4. Push a commit, or click Update branch if the branch is behind. Either gives GitHub a new head to test. (In Pyor, Update branch is in the status pill in the pull request header.) If you are behind the base, our guide to the out-of-date branch message covers merge versus rebase.
  5. If nothing moves, check githubstatus.com.

Once the check finishes and finds a conflict, the merge button stays off until the conflict is resolved. GitHub’s merge conflict docs say simple line conflicts can often be resolved on GitHub, while more complex ones must be resolved in a local clone and pushed back to the branch.

How do I know if it is a GitHub outage?

githubstatus.com lists Pull Requests as its own component, next to Git Operations, API Requests, Webhooks, and Actions. If Pull Requests or API Requests shows degraded performance, the delay is GitHub’s. I’d leave the branch alone until the incident clears, since a rebase or force-push during an outage just hands GitHub another merge to test.

If you turned on auto-merge, you can stop checking the tab. It merges the pull request once all merge requirements are met.

What blocks the merge after the check finishes?

A finished check doesn’t mean you can merge. A required status check that never reports leaves you on “Expected: Waiting for status to be reported”, and a ruleset block shows up as repository rule violations.

Frequently asked questions

How long should "Checking for ability to merge automatically" take?

GitHub does not publish a time. The REST docs only say that when mergeability is unknown, GitHub has started a background job, and you should give it time to finish and ask again. Reload the pull request page after a moment. If it never finishes, check githubstatus.com for a Pull Requests incident.

What does mergeable: null mean in the GitHub API?

It means GitHub has started a background job to compute whether the pull request can merge and the job has not finished yet. Wait, then request the pull request again. In GraphQL the same state is UNKNOWN, which GitHub describes as mergeability that is still being calculated.

Is "Checking for ability to merge automatically" the same as a merge conflict?

No. The check is GitHub working out whether a conflict exists. When it finishes and finds one, the pull request shows as conflicting and the merge button stays off until the conflicts are resolved. Simple line conflicts can be fixed on GitHub; more complex ones need a local clone.

Review your next PR in Pyor.

Pyor’s merge box updates the branch, merges with any method the repo allows, turns on auto-merge, or joins the merge queue, in the same window you review in. Free for individuals, and it talks to GitHub straight from your machine.