PR Throughput Overview

Learn about your organizations code delivery practices and how they've changed over time.

What is PR Throughput? 

PR Throughput counts the number of merged PRs a group has collectively authored in a given time period. It is an indication of how frequently code changes occur, and whether that comes in a consistent cadence. PR throughput is helpful for all teams to better understand their ability to consistently deliver code. To go a layer deeper and explore the team’s ability to deliver to end users, take a look at the Deployment Frequency metric that leverages CI/CD data.

Example of PR Throughput:

If 5 PRs are merged to a Staging branch, and then these are pushed to the Production branch with an additional pull request, that would count as 6 PRs merged.

Trend

See your organization's throughput trend over time. This chart shows the number of PRs merged throughout the date range selected.

💡 Tip: the main thing to look for is consistency here. Merging often helps keep your team's in practice. 

Merged PRs

Leverage this view to understand whether PRs are Complex to Review or were Delayed in the development process.
 

Definitions

Complex PRs

PR complexity is calculated by looking at the number of lines added and deleted, number of files, and refactors. Each PR is estimated to be either “Complex” or “Not Complex” to review in this metric, and is measured to have low, medium, or high complexity.

Delayed PRs

Two factors determine whether a PR has become “delayed” - the PR Complexity, as well as time spent in the Waiting / In Review phases. The table below shows how long a PR must be stuck in review to be considered delayed based on its complexity.

 

PR Complexity Delayed After
Not Complex 3 business days
Complex 5 business days

 

Top Repos 

Understand where your teams are merging code. This chart shows the top repos by number of PRs merged, and what fraction that represents for your team.

 

Breakdown Table

Pivot the data to understand how many PRs are merged by different groupings, as well as PR Complexity and what fraction of PRs were delayed along the way.