Why it matters
Small PRs are easier to review, safer to ship, and faster to merge. When the distribution skews to Large/Huge, reviews get superficial, merge conflicts pile up, and cycle time balloons. This chart makes the team’s “default PR size” visible so you can push culture toward smaller batches.What good looks like
Most merged PRs should sit in the Tiny and Small buckets. Large and Huge should be the exception and tied to clear structural work (big migrations, codegen), not regular feature development.How to improve
- Break tickets into vertical slices before coding starts.
- Try stacking PRs for dependent changes instead of one megabranch.
- Separate refactors and moves from behavior changes. Ship the mechanical change, then the logic change.
- Keep CI fast and painless so the cost of shipping one more PR is low.
How the chart is built
- Each merged PR is bucketed by total lines added and deleted using the size thresholds in your workspace settings (the same Tiny → Huge scale as elsewhere in Sweetr).
- The stacked bars show how many PRs fell in each size bucket in each time period.
- The white line is the average total lines changed for merged PRs in that same period.