Sweetr Docs home page
Search...
⌘K
Login
Get Started
Get Started
Search...
Navigation
Team Insights
PR size distribution
Documentation
Repository
Give Feedback
Welcome
Intro
Get Started
Features
Alerts
Digests
Work Log
Pull Requests
Work In Progress
Teams
People
Code Reviews
Team Insights
Intro
Code review distribution
PR size distribution
Cycle time
Time to first review
Time to approve
Time to merge
Automations
Integrations
About Us
Principles
Open Source
Data-privacy & Security
Roadmap
On this page
Demo
Size
Insights
What good looks like
How to improve
Team Insights
PR size distribution
Breakdown of team’s Pull Request size and frequency.
Demo
Size
The pull request size is calculated based on the amount of lines changed.
Tiny
< 20 lines changed.
Small
20~100 lines changed.
Medium
100~250 lines changed.
Large
250~500 lines changed.
Huge
> 500 lines changed.
Customize how PR size is calculated in your workspace settings.
Insights
This chart can help you measure and answer questions like:
Is the team striving for small Pull Requests?
Is review or merge time slow because of big Pull Requests?
What good looks like
Ideally, most of Pull Requests should be small or tiny.
They are easier to review.
They have fewer bugs.
They are picked up and approved faster.
They have fewer merge conflicts.
Striving for smaller Pull Requests can reduce your team’s cycle time and help your team ship product faster.
How to improve
There are some strategies that can help your team aim for smaller Pull Requests.
Visit this data during retrospectives and discuss options with the team.
Keep CI/CD process fast and painless.
Break down tickets into smaller pieces.
Try
stacking
Pull Requests.
Ready to unlock continuous improvement in your team?
Try now
Code review distribution
Cycle time
Assistant
Responses are generated using AI and may contain mistakes.