Every commit scored for change-risk against this repo's own history, so 'elevated' means elevated here rather than on some global curve.
Needs review
1 commits sit in this repo's top risk tercile, which is 25% of the 4scored. The cut is drawn against this codebase's own history rather than a global curve, so a quiet repo still fills its top band, and here it starts at 9.8 out of 10. What pushes a commit up is size and spread together: a large change confined to one area scores below a smaller one scattered across a dozen files.
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.
Ranked by change-risk, highest first. Priority is a tercile of this repo's own distribution, so a quiet repo still fills its top band.
| # | Commit | Author | When | Lines | Risk | Top driver |
|---|---|---|---|---|---|---|
| 1 | a0a4dd350.0.0 | substrate-bot | 5mo ago | +3.4K -0 | 88%Elevated | large diff (many lines added) |
| 2 | 22b1938f📝 Add docstrings to `000` | coderabbitai[bot] | 5mo ago | +394 -29 | 63%Typical | large diff (many lines added) |
| 3 | f929911fvids | substrate-bot | 3mo ago | +259 -1 | 38%Typical | large diff (many lines added) |
| 4 | 5f25fde80.0.0 | substrate-bot | 5mo ago | +164 -0 | 13%Below typical | large diff (many lines added) |
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 4 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.
Repowise tracks change history across 6 files in quazfenton/youtubeSync. In the last 90 days 1 file was touched, 1 times in total, most often monitor.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.
