GitHub Metric
Engineering
PR Approval Rate = PRs Approved on First Review / Total PRs Reviewed × 100
Pull Request Approval Rate measures the percentage of pull requests that are approved without requiring changes on their first review cycle. A high rate indicates well-aligned coding standards, effective planning, and good communication between authors and reviewers.
GitHubEngineeringPull Request Approval Rate
Pull Request Approval Rate measures the percentage of pull requests that are approved without requiring changes on their first review cycle. A high rate indicates well-aligned coding standards, effective planning, and good communication between authors and reviewers.
How to calculate pull request approval rate
Why pull request approval rate matters for GitHub users
A low first-review approval rate signals misalignment between what authors produce and what reviewers expect. This wastes time on both sides - authors rework code while reviewers re-review, extending cycle times and reducing throughput.
For GitHub teams, tracking approval rate reveals whether coding standards are clear, whether PR descriptions provide sufficient context, and whether pair programming or design reviews upstream could prevent downstream churn.
Understand and act on pull request approval rate with KPI Tree
Sync pull request review data from GitHub into your warehouse and compute approval rate in KPI Tree. Link it to code review quality score and cycle time to understand its impact on delivery speed.
Assign RACI ownership to team leads and use the metric to guide improvements in PR templates, coding standards documentation, and upstream collaboration practices.
Get started with your GitHub data
MCPPull metrics from GitHub directly through the Model Context Protocol.
Connect your existing warehouse where GitHub data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related GitHub metrics
Code Review Quality Score
EngineeringMetric Definition
Code Review Quality Score evaluates the substantiveness of pull request reviews by weighting factors such as comment depth, suggestions made, files reviewed versus files changed, and time spent. It distinguishes meaningful reviews from rubber-stamp approvals. Higher scores correlate with fewer post-merge defects.
Code Review Velocity
EngineeringMetric Definition
Code Review Velocity = Median(First Review Timestamp − PR Ready Timestamp)
Code Review Velocity measures the elapsed time from when a pull request is opened or marked ready for review to when the first substantive review is submitted. It is a key driver of lead time for changes. Long review waits are one of the most common causes of developer context-switching.
Pull Request Bottleneck Analysis
EngineeringMetric Definition
Pull Request Bottleneck Analysis examines the stages of the PR lifecycle - authoring, review wait, review-in-progress, CI execution, and merge - to identify where delays accumulate. It transforms aggregate cycle time into an actionable breakdown that pinpoints specific process failures.
Code Churn Rate
EngineeringMetric Definition
Code Churn Rate = Lines Re-changed Within N Days / Total Lines Changed × 100
Code Churn Rate quantifies the percentage of lines changed within a short window after their initial commit. High churn often indicates unclear requirements, premature coding, or inadequate design reviews. It is a proxy for wasted engineering effort.
All GitHub metrics
Branch Lifecycle AnalysisBug Fix RateCode Churn RateCode Coverage TrendCode Quality Trend AnalysisCode Review Quality ScoreCode Review VelocityCommit FrequencyDeployment FrequencyDeveloper Contribution PatternsDeveloper Productivity ScoreDevOps Pipeline EfficiencyDiscussion Engagement RateFeature Development Cycle TimeIssue Resolution TimeLead Time for ChangesOpen Source Contribution AnalysisPull Request Bottleneck AnalysisRelease VelocityRepository Health ScoreSecurity Alert Resolution TimeSecurity Vulnerability TrendsSprint Velocity TrackingTeam Collaboration IndexTechnical Debt AccumulationEmpower your team to understand and act on GitHub data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
