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
8not verified
| PR | Base | Merged | Verification | Detail |
|---|---|---|---|---|
| #4666 feat(home): rebuild .com landing page as AI marketing platform | main | 2026-04-16 | not verified | merged before verification existed |
| #4667 Claude/fix domain pricing q sr lp | main | 2026-03-29 | not verified | merged before verification existed |
| #4668 Rebrand Dominat8 from aggressive to professional positioning | main | 2026-03-29 | not verified | merged before verification existed |
| #4669 feat: Dominat8 killer landing page — dark theme, toxic green, 7-secti… | main | 2026-03-28 | not verified | merged before verification existed |
| #4670 Rebuild marketing homepage with aggressive AI-first positioning | main | 2026-03-28 | not verified | merged before verification existed |
| #4671 Remove marketing pages and clean up unused config files | main | 2026-03-23 | not verified | merged before verification existed |
| #4675 fix: resolve all CI/workflow failures for green PR builds | main | 2026-03-22 | not verified | merged before verification existed |
| #4673 fix: resolve all CI failures blocking PR merges | main | 2026-03-22 | not verified | merged before verification existed |
Showing the last 8 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.