Turnaround dashboards for engineering leadership
New admin turnarounds page surfaces median review time per repo so leads can spot slowdowns before they block releases.
Changelog
The last ten updates to Mergent — the features, fixes, and small polish moves that shipped to production.
New admin turnarounds page surfaces median review time per repo so leads can spot slowdowns before they block releases.
Merge rules can now require an extra approver on changes to billing or data schemas, and the v2 schema editor highlights those files.
Capture the team's review conventions inline so they stay discoverable next to the rules that enforce them in the auto-merge pipeline.
Export the full auto-merge audit log to CSV so postmortems no longer wait on a manual query for the merge decisions of last month.
A new repo-health table summarizes review latency and merge depth across every connected repo, so platform teams can prioritize where reviews are stalling.
A dedicated inbox for PRs the agent held back, each tagged with the merge rule or test failure that stopped it so the next move is obvious.
The install callback now retries once on transient GitHub API failures so first-time repo connects almost never need a manual re-install.
New accounts pick a starting risk threshold during onboarding so the first week's PRs get the right level of review from day one.
Reviewer comments now carry a confidence flag so the team can spot tentative notes versus solid findings without re-reading the diff.
A weekly digest summarises which PRs the agent merged and which it held, so the team starts Monday with a clean picture of last week.