Review analytics: what Auditor finds, what your team acts on, and who does what
The Auditor page has an Analytics tab: how often your team acts on findings, findings posted, cost per pull request and time to merge, against the period before; findings by how they ended; each kind of finding by how often it is acted on, with what tuning muted; and every repository or author with findings posted, resolved and open, reviews started automatically or asked for, commands, previews and cost.
Each repository has a page of its own: every way Auditor was started there, each command and question included, with who started it and what came of it; the people who worked with it and what each fixed, dismissed and taught it; a timeline of feedback, rules and tuning; every setting in effect with where it comes from; models used; and merge check results.
Commands, previews, pull request authors and who decided a finding are counted from today; reviews, findings, learnings, tuning and costs go back further.
More in Analytics.