repowiserepowiseEvery commit, led by what it did to code health. Review priority from the diff's shape stays alongside as context.
Past month
100% were chores.
Health counts cover the 0 of 1 commits the current analyzer has read; the rest fill in as updates run.
No wins recorded in this window yet. Resolved findings, healthier files and landed refactorings show up here as they happen.
Commit categories over time, read off the subject line. Fixes carry the accent because that is the series this chart exists to show.
How this repo's commit mix shifts over time.
Newest first, each led by what it did to code health. The filters narrow the whole repository, not the page.
| Health | Commit | Author | When | Lines | Review priority |
|---|---|---|---|---|---|
| Not yet analysed | db3fdaeaMerge branch 'fix/GBAT-644-removed-name-from-operators-daily-reminder' into 'master' | Pavel Potseluyevnew contributor | +185.7K -0 | 50th · Typical |
Two views of the same model: where the cuts fall, and what commit shape lands you above them.
Every scored commit, binned on the raw 0 to 10 score rather than the percentile. Percentile ranks are uniform by construction, so that axis has no shape to draw. The dashed lines are the tercile cuts behind each row's priority pill.
The 1 most recent commits, on their own recency sample rather than the feed above: that defaults to risk-sorted, so reusing it would plot only the top tercile and call it the spread. Big and scattered is what the model penalises. Click a dot to open it.
