Loading…
LoadingLoading…
LoadingAgent A and Agent B open pull requests in parallel. Each change can look reasonable in isolation. Together, they may still need a human to decide which change lands first and what the second PR should rebase onto.
The PR changes a shared rule. Reviewed alone, it has a clean diff and green CI.
Veripsa saw no open-PR overlap for this PR. Continue the normal review, CI, and branch-protection merge path.
Different goal, overlapping behavior. The useful question is not whether either PR is bad; it is whether the landing order deserves a look before both reach main.
This PR may need to wait behind PR A. Land the earlier change, then rebase and review this PR once against the updated base.
A material warning is posted as an action_required check. Veripsa adds no routine ACK step: if the check is not required, it does not prevent the merge. A team can optionally add veripsa-ack to record a reviewed exception and move this check to neutral.
Veripsa does not replace review, CI, or your merge queue. It puts the cross-PR question in front of the people and agents doing the merge.
Each PR may still pass its own checks, but the second merge can force avoidable rework because it never incorporated the first change.
Land PR A first, rebase PR B once, and make the behavior decision deliberately while the work is still reviewable.
Install the GitHub App once and matching PRs receive checks and managed comments automatically. There is no agent-side plugin, command sequence, or ACK ceremony. Optional guidance is available only for teams that want merge-capable agents to interpret the signal consistently.
Veripsa Core is designed to surface likely open-PR overlap before merge. It is advisory, content-free, not an AI reviewer, not CI, and not a merge queue. It coordinates one repository at a time today.
