Dependency PR automerge blocked by required checks in CI

By Daniel Zoghalchali·Latchkey

Automerge for both Dependabot and Renovate only fires once every required status check passes. If a required check never runs on the update branch, or its context name does not match branch protection, the PR waits forever regardless of the automerge setting.

What this error means

A dependency PR shows "Waiting for status to be reported" or "Required check has not passed", and automerge does not complete even though the diff is green in the checks that did run.

Required statuses must pass before merging
Expected - Waiting for status to be reported (required): build

Common causes

A required check never runs on the update branch

The workflow does not trigger on the events these bots raise, so a required context stays in the pending state indefinitely.

The required context name does not match

Branch protection requires a context name that differs from the actual check name (job vs workflow name), so it is never satisfied.

How to fix it

Align triggers and context names

1. Ensure required checks trigger on pull_request so bot PRs run them.
2. Copy the exact check name into the required contexts list.
3. Remove required contexts that no longer produce a status.

on:
  pull_request:
jobs:
  build:            # this job name is the required context
    runs-on: ubuntu-latest
    steps:
      - run: make test

Prune stale required checks

If a required check was renamed or removed, update branch protection to require only checks that still report a status.

How to prevent it

• Trigger required checks on pull_request so bot PRs run them.
• Keep required context names in sync with job names.
• Remove required contexts for checks that no longer run.

Frequently asked questions

Related guides

References

• GitHub Actions documentation