Try or ByeTry or Bye

Linear Ready for Merge Not Triggering

Workaround available Web Updated October 21, 2026

Quick answer

GitHub only reports a PR as ready to merge when reviews or checks are required and all checks pass. Any failing check, even an optional one, blocks it; add branch protection and a review automation.

Most likely fix: Require reviews or checks on the branch.

Symptoms

Issues skip the 'ready for merge' status or the status chain stalls in review.

Why it happens

  • Any failing check makes GitHub mark the PR unstable
  • No branch protection rules, so the PR is always considered mergeable
  • No 'review request or activity' automation configured

How to fix it

Try these in order — the most common fix is first.

  1. 1. Require reviews or checks on the branch

    1. In GitHub repo settings, add a branch protection rule for the target branch
    2. Require a review or a status check

  2. 2. Fix or remove failing optional checks

    1. Open the PR checks tab
    2. Fix failing checks, even non-required ones, and re-test with a green PR

  3. 3. Add a review automation in Linear

    1. Settings > Team > Workflows & automations
    2. Configure the 'review request or activity' trigger alongside 'ready for merge'

This guide also covers

  • linear ready for merge
  • linear github status automation

Still not working?

If Linear keeps failing, you're not alone. See every Linear problem users report or the alternatives people switch to.

Other Linear errors