Total PRs Merged

Last updated: October 27, 2026

Total PRs Merged is the number of pull requests (PRs) your contributors merged in the selected date range. It's a raw count, not a rate, so it grows with team size and with the length of the range.

Why it matters

  • Delivery volume: a simple baseline of how much change your team integrates, useful for sprint totals and stakeholder reporting.

  • Capacity planning: 4–6 sprints of history give you a typical range to plan against.

  • Onboarding: shows when new hires start merging code regularly.

  • A denominator for other metrics: % of PRs Merged Without Review, % of PRs Merged with Tests, PR Link Rate, Comments Received / PR, and PR Revert Rate all divide by it.

How it works

Total PRs Merged = count of PRs where
  status = merged
  author is marked Contributor (or is a dev agent Span tracks)
  merge time falls in the selected date range

  1. Span syncs PRs from your version control system.

  2. Span maps each PR author's account to a person or dev agent. PRs from accounts it can't map drop out, which covers most bots.

  3. Span dates each PR by its merge time and puts it in the period that contains that time.

  4. A team's total is the sum over its members. A person's total covers the PRs they authored.

PR statuses:

Status

Meaning

Counted?

Merged

Integrated into the base branch

Yes

Open

Not merged yet

No

Closed

Closed without merging

No

Reverted

Merged, then undone by a later PR

No. It moves to Total Reverted PRs

Where to find it: Insights > Productivity > Velocity > Delivery. It also appears in team and person Metrics tabs, custom reports, and custom dashboards. Click the chart to open the matching merged PRs in Catalog.

Breakdowns: person, team, job level, job title, job family, location, and repository, by day, week, month, or quarter.

Related variants: PRs merged / week turns the count into a per-person weekly rate that accounts for team size and time off. Use it to compare teams or periods. Use Total PRs Merged for absolute totals.

Setup

  1. Connect your version control system: GitHub, GitHub Enterprise Server, GitLab, or Azure DevOps. Bitbucket Cloud is also supported; Span turns it on for your organization on request.

  2. In Settings > People management, set Code Contribution to Contributor for people who write code and Non-contributor for those who don't, such as most managers.

  3. Under Settings > Metrics, add any repositories, branches, or Git usernames to ignore.

  4. Set up your teams so team totals roll up correctly.

Things to know

  • Reverted PRs leave the count. When a revert PR merges, Span changes the original PR's status from merged to reverted, and the original no longer counts in Total PRs Merged. The revert PR itself counts as a merged PR. Worked example: your team merges 45 PRs in a sprint. Two weeks later, a revert of one of them merges. The sprint's total drops to 44, and the revert PR counts in the period it merged.

  • Past totals can change. A new revert, a new ignore pattern, or switching someone to Non-contributor changes historical totals, because Span applies the current settings to all history.

  • Span counts fewer PRs than a raw GitHub search. Span leaves out reverted PRs, PRs from people marked Non-contributor, ignored repositories, branches, and usernames, and accounts it can't map to a person.

  • PRs into any branch count unless the branch matches an Ignore Branches pattern. Span has separate patterns for base and head branches.

  • Time off doesn't remove PRs here. Total PRs Merged keeps PRs merged on out-of-office days. PRs merged / week removes them.

  • It measures volume, not value. It says nothing about size, complexity, quality, or review depth. Read it with PR Size, Weighted PRs / week, PR Revert Rate, and % of PRs Merged with Tests. Use it for team-level patterns, not individual performance reviews.

Related articles

PRs Merged / Week

PR Revert Rate

Weighted PRs/Week

What determines contributor status in Span user profiles?

Need help?

Contact your Span account team or reach out to support@span.app.