Readiness
Checks, approvals, CODEOWNERS, stale approval state, and unresolved blockers are visible before a PR is queued.
One screen shows whether a pull request can merge, which lane it belongs to, what policy governs it, and what happens next.
Checks, approvals, CODEOWNERS, stale approval state, and unresolved blockers are visible before a PR is queued.
Lanes stay explicit. Operators can fast-track, pause, retry, or requeue without leaving the same surface.
Rulesets, merge methods, labels, priority rules, and freeze windows stay attached to the lane that enforces them.
Rulesets and queue lanes mapped to the same console.
Passing checks, approvals, and no unresolved blockers.
Trunk, release, and hotfix move independently.
No hidden freeze state before an operator enqueues work.
mobile/api-gateway
growth/webapp
infra/payments
Mirrors the GitHub ruleset and shows the exact owning team before queue entry.
Urgent labels jump ahead without rewriting queue order by hand.
Lane pause preserves queue order while operators stabilize production.
Release lane resumed after deploy verification completed.
payments#211 received a new push and needs a fresh codeowner sign-off.
Urgent fix label moved api-gateway#4121 to the head of trunk.
Keep queue, policy, and evidence in one place.
Show blockers before a pull request enters a lane.
Prefer explicit rules over hidden state.
Keep the screen fast to scan.
Required checks and merge_group listeners are wired to the expected app source.
Stale approvals, CODEOWNERS, and unresolved request-changes are visible before queueing.
Queue lane, merge method, label rules, and freeze windows are shown on the same screen.
Visible per lane, not buried in external dashboards.
Retries, eject reasons, and lane hotspots stay traceable.
Flaky CI gets isolated before it distorts merge velocity.
From ready PR to lane commit, with no extra modal maze.