Sweetr Docs home page
Search...
⌘K
Login
Get Started
Get Started
Search...
Navigation
Team Insights
Time to merge
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
Insights
What good looks like
How to improve
Team Insights
Time to merge
Time elapsed between approval and merge.
Demo
Insights
This chart can help you measure and answer questions like:
Are Pull Requests merged promptly?
Are the recent process changes effective?
Are there any recurring patterns or periodic fluctuations?
What good looks like
Ideally, most small Pull Requests should be merged within a hour of it being approved. Teams should prioritize finishing work over starting new things.
How to improve
There are some strategies that can help your team’s time to merge.
Visit this data during retrospectives and discuss options with the team.
Keep CI/CD process fast and painless.
Prioritize finishing open work vs starting new things.
Ready to unlock continuous improvement in your team?
Try now
Time to approve
Intro
Assistant
Responses are generated using AI and may contain mistakes.