ccantynz/48co.nz-dictation
☆ 0
CodeIssuesPull RequestsActionsSecurityInsights
✨ AI
Understand
Explain codebaseAsk AIChat with repoClaude sessionsNL searchSemantic searchArchaeologyDebt mapDocs tracking
Build
Spec to PRWorkspaceGenerate testsPropose migrationDev environmentCodebase migrator
Ship
Preview URLsAI release notesAI changelog
More
Repository
CommitsBranchesTagsReleasesPackagesSymbolsStale branches
Planning
MilestonesProjectsDiscussionsWikiContributors
Delivery
GatesMerge queueMerge checksDeploymentsPipelineAgents
Activity
Health reportPulsePush log
Settings
← Back to pull requests
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
4not verified
PRBaseMergedVerificationDetail
#3948 Refactor: Extract login page and implement feature panels architecturemain2026-04-22 not verifiedmerged before verification existed
#3949 Add autonomous build rules to CLAUDE.md + scaffold new UI featuresmain2026-04-05 not verifiedmerged before verification existed
#3950 Claude/debug site loading i9mb4main2026-04-01 not verifiedmerged before verification existed
#3951 Update dependenciesmain2026-04-01 not verifiedmerged before verification existed

Showing the last 4 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.