ready

Show PRs that are ready to merge — approved, CI passing, no conflicts.

A merge-ready PR is one that has:

✅ Not a draft
✅ CI/CD checks passing (or pending)
✅ No merge conflicts
✅ Is mergeable (GitHub says so)

When to Use

Morning check: “Which PRs can I merge right now?”
Release planning: “What’s blocking the merge queue?”
Dashboard prep: “Get a quick list of deployable changes”
QA handoff: “Verify which PRs are good to go”

Synopsis

prctrl ready [OPTIONS]

Options

Flag	Description	Default
`--pr, -p <NUMBER>`	Target a specific PR by number	-
`--pr-numbers <NUMS>`	Check multiple PRs (comma-separated)	-
`--all, -a`	Check all pending reviews	`false`
`--repo <NAME>`	Filter to specific repository (partial match)	All repos
`--author <USER>`	Filter by author username (partial match)	All authors
`--since-days, -s <DAYS>`	Only show PRs created since N days ago	All PRs
`--priority, -P`	Show priority scores (1-5 stars) based on age and size	`false`
`--json`	Output as JSON for scripting	`false`

How It Works

The ready command analyzes your pending review PRs and checks each one’s merge readiness:

Fetches CI status via GitHub’s combined status API
Checks merge conflicts using GitHub’s mergeable field
Filters out drafts (not ready for merge)
Sorts by age — oldest mergeable PRs first

A PR is considered “ready to merge” when:

draft = false
ci_status = "success" or "pending"
mergeable = true (not false)
has_conflicts = false

Output

🚀 Merge Readiness — 8 PRs total, 3 ready to merge
──────────────────────────────────────────────────

  ✅  #4821  Fix authentication bug
      👤 alice  •  📦 +340/-25  •  ⏱️ 2 days  •  ✅ CI
      📁 myorg/frontend  🔗 https://github.com/myorg/frontend/pull/4821

  ✅  #4815  Update dependencies
      👤 bob  •  📦 +50/-10  •  ⏱️ today  •  ✅ CI
      📁 myorg/shared  🔗 https://github.com/myorg/shared/pull/4815

  ⏳  #4809  Refactor API gateway
      👤 carol  •  📦 +1200/-200  •  ⏱️ 5 days  •  ⏳ CI pending
      📁 myorg/backend  🔗 https://github.com/myorg/backend/pull/4809

──────────────────────────────────────────────────
  💡 Ready = not draft + CI passing + no conflicts
  💡 Use `--json` for scripting

With Priority Flag

When --priority is enabled, each PR shows its priority score:

🚀 Merge Readiness — 8 PRs total, 3 ready to merge
──────────────────────────────────────────────────

  ✅  #4821  Fix authentication bug  ⭐⭐⭐⭐
      👤 alice  •  📦 +340/-25  •  ⏱️ 2 days  •  ✅ CI
      📁 myorg/frontend  🔗 https://github.com/myorg/frontend/pull/4821

  ✅  #4815  Update dependencies  ⭐
      👤 bob  •  📦 +50/-10  •  ⏱️ today  •  ✅ CI
      📁 myorg/shared  🔗 https://github.com/myorg/shared/pull/4815

──────────────────────────────────────────────────
  💡 Ready = not draft + CI passing + no conflicts
  💡 Priority based on age and size
  💡 Use `--json` for scripting

Examples

# Interactive: show all pending PRs with readiness status
prctrl ready

# Check specific PR by number
prctrl ready --pr 1234

# Check multiple PRs at once
prctrl ready --pr-numbers 1234,5678,9012

# Check all pending reviews (non-interactive)
prctrl ready --all

# Filter to specific repo
prctrl ready --repo frontend

# Filter by author
prctrl ready --author alice

# Filter by repo and author combined
prctrl ready --repo backend --author bob

# Only show PRs from the last 7 days
prctrl ready --since-days 7

# Only show PRs from today
prctrl ready --since-days 1

# Show priority scores to identify most urgent ready PRs
prctrl ready --priority

# JSON output for scripting
prctrl ready --json

# Combine with other commands
prctrl ready --repo backend | grep "✅"

Tips

Use --json for integration with dashboards or automation scripts
Pipe to grep "✅" to get just the ready PRs
Ready PRs are sorted by age — oldest first
CI “pending” is counted as ready (in progress, not failed)
Combine with browse to quickly open merge-ready PRs

ci — Detailed CI/CD pipeline status
conflicts — Find PRs with merge conflicts
browse — Open PRs in browser

Keyboard shortcuts

PRCtrl