Which open PR should land first?

Why landing order is its own question

Knowing two PRs overlap is one question. Knowing which to land first is another. The order matters because the second PR’s rebase is the one that does the work — one order can make the follow-up review and rebase smaller, while another can turn one clean-looking change into multiple rounds of rework.

A pure collision check answers “these two PRs overlap.” A merge queue answers “merges happen one at a time.” Neither answers “land this one first.” That third question is what closes the loop in a multi-agent workflow — it’s the decision the agent can’t make for itself.

What a useful suggested-order tool looks like

A useful suggested-order tool has four properties. (1) Open-PR aware. It knows when open PRs may overlap, so the order is grounded in the current review set, not arbitrary timestamps. (2) Per-PR visible.The suggested order shows up on each PR’s check, where the agent and the reviewer already are. (3) Advisory.It’s a suggestion; the human (or the merge queue) makes the call. (4) Readable.The suggestion is short enough for a human to understand in the check message — not a black-box ranking.

That category sits next to merge queues and CI gates but doesn’t replace either. A queue still serialises; CI still validates; the suggested order tells you which PR to put first into either.

How Veripsa Core posts a suggested order

Veripsa Core is a GitHub App. It uses minimal operational metadata needed to post advisory checks while keeping file bodies out of Veripsa storage.

On covered PRs, Core evaluates open-PR context in that repo. When likely overlap is observed, both PRs see an advisory check — Clear, Heads up, Wait in line, or Unknown — with a suggested land order. The guidance is intentionally short and advisory. You (or your merge queue) decide what merges.

• Suggested, not enforced. The order shows up on each PR’s check; the human or the merge queue makes the call.
• Grounded in open PRs. The suggestion is based on likely overlap in the current review set, not on arbitrary timestamps.
• Readable. The basis is something a human can read in the check message — not a black-box ranking.
• Content-free. Uses minimal operational metadata for advisory checks. File bodies are not stored.
• Same-owner per-repo today. Cross-repository ordering is on the roadmap, not shipped.