Repository · Merge safety
Post-merge verification
After every merge the platform re-checks that main (or the PR's base) actually holds what a correct merge would leave there: the previous tip is still an ancestor, the PR head is in, the tree matches what git computes, and the objects exist. Merged PRs from before this verifier existed show as not verified — recompute one to check it now.
0verified
0failed
6not verified
| PR | Base | Merged | Verification | Detail |
|---|---|---|---|---|
| #3830 Claude/continue previous work h hk dk | main | 2026-04-18 | not verified | merged before verification existed |
| #3835 feat: Implement Intelligent Plugin Conflict Detector WordPress plugin | main | 2026-04-18 | not verified | merged before verification existed |
| #3831 Claude/check build status 7 cw rz | main | 2026-04-18 | not verified | merged before verification existed |
| #3832 Add pre-update simulation, reporting, and export features | main | 2026-04-16 | not verified | merged before verification existed |
| #3833 Claude/woocommerce conflict detector tb9 gg | main | 2026-04-14 | not verified | merged before verification existed |
| #3834 Build complete Jetstrike Conflict Detector plugin | main | 2026-04-13 | not verified | merged before verification existed |
Showing the last 6 merged pull requests. Verdicts are audit-log rows (merge.verified / merge.verification_failed) — immutable, written by the merge path itself. A recompute on an older merge runs in historical mode: it checks the merge commit is still reachable from the current base tip rather than that the tip is the merge commit.