Time to merge

Tags: Flow

Time to merge is the average time in hours from when pull requests are created to when they are merged, rounded to the nearest tenth of an hour. 

Note: If your Pull request tracking is set to First commented, the pull request creation time is the time of the first comment. Change this setting on the configurations page.

Which reports use Time to merge?

You can see Time to merge in PR resolution and Submitter fundamentals.

back to top

What does Time to merge measure?

Time to merge tells you how long pull requests are in review. This is a key health metric for flow efficiency. 

It’s an objective view of the time it takes to vet and improve the development work your team is doing.

Long-running pull requests are costly to your business. Paying attention to Time to merge results in a decrease in delayed releases.

back to top

How is Time to merge calculated?

Time to merge is calculated as the sum of all Times to merge for all merged pull requests created by included individuals divided by the total number of merged pull requests created by included individuals.

This average is rounded to the nearest tenth of an hour.

This calculation is the same whether calculating Time to merge for an individual, a team, or an organization.

back to top

What data is included in Time to merge?

A pull request is counted toward Time to merge as long as it is merged. It does not matter whether it’s merged from one feature branch to another or is merged into the main branch.

Pull requests are not counted toward Time to merge if:

  • they are created by a user who is excluded from reports

  • they are created by a hidden user

  • they are an excluded pull request

  • they are from a deleted repository

Note: User view rights and permissions also impact how specific users will see Time to merge.

back to top

If you need help, please email support@pluralsight.com for 24/7 assistance.