Connect the GitHub App
Install prmerger on the repositories or organizations that own the pull requests you want to control.
Documentation
Run merges with clear rules and visible state.
Merge readiness, queue lanes, policy state, and evidence for GitHub pull requests. prmerger keeps merge operations clear and visible.
Mirror your merge rules
Map required checks, CODEOWNERS, merge methods, labels, and freeze windows into the same readiness model.
Activate queue lanes
Create explicit lanes for trunk, release, or hotfix work so operators can see capacity and risk before enqueueing.
First Run
Setup is short.
Paste a GitHub pull request URL
Start from the homepage with a PR link. If you are not signed in, prmerger preserves the PR and routes you through GitHub auth.
Complete repository access
If the target repository is not connected yet, finish the GitHub App install for that exact repo or organization.
Approve the workflow once if needed
Protected default branches may require a one-time workflow pull request before the first readiness check can dispatch.
Operating Rules
Keep rules visible.
Checks and merge_group stay explicit
Required checks, merge queue events, and app-scoped rules stay visible so operators can see exactly what will block the lane.
Approvals never hide behind stale state
CODEOWNERS, request-changes, and invalidated approvals are part of readiness instead of being scattered across several tabs.
Queue controls are operational controls
Pause, retry, requeue, and priority are designed as first-class lane actions rather than emergency workarounds.
prmerger Console
Queue state, policy, and evidence.
Current view
Workspace
At a glance18
Repos onboarded
Rulesets and queue lanes mapped to the same console.
42
Ready PRs
Passing checks, approvals, and no unresolved blockers.
3
Queue lanes
Trunk, release, and hotfix move independently.
0
Incident pauses
No hidden freeze state before an operator enqueues work.
Queue lanes
Ready before enqueueapi-gateway#4121 running
Ship OAuth token refresh safely
mobile/api-gateway
trunk
4 min
merge_group + deploy smoke
webapp#1198 waiting
Bundle checkout locale fixes
growth/webapp
trunk
8 min
ui, unit, playwright
payments#211 blocked
Requeue refund webhook patch
infra/payments
release
Needs approval
prod hotfix rules
Policy map
Rules on screenRequire codeowner approval on payment paths
activeMirrors the GitHub ruleset and shows the exact owning team before queue entry.
Fast-track urgent fixes with lane priority
activeUrgent labels jump ahead without rewriting queue order by hand.
Pause trunk during deploy incidents
watchingLane pause preserves queue order while operators stabilize production.
Event rail
Action history09:12
Lane pause cleared
Release lane resumed after deploy verification completed.
09:06
Approval invalidated
payments#211 received a new push and needs a fresh codeowner sign-off.
08:58
Priority lane activated
Urgent fix label moved api-gateway#4121 to the head of trunk.
Readiness
See blockers before using the queue.
Checks matched
Required checks and merge_group listeners are wired to the expected app source.
Approvals current
Stale approvals, CODEOWNERS, and unresolved request-changes are visible before queueing.
Policy aligned
Queue lane, merge method, label rules, and freeze windows are shown on the same screen.
FAQ
The practical questions teams ask during rollout.
Do we have to replace our existing CI?
No. prmerger is designed to sit on top of the checks and protection rules your team already trusts.
Does the workflow need to exist on the default branch?
Yes. GitHub requires the workflow file to exist on the default branch before manual dispatch can run successfully.
Does this replace human review?
No. prmerger sits after review and before merge. It makes queue, policy, and readiness state easier to operate.