Team & People Metrics

These metrics appear in the Team Insights leaderboard and Contributor Profile pages. They focus on individual delivery patterns rather than repository-level aggregates.

Team Leaderboard Columns

Column	Calculation	What to look for
PRs Merged	Count of PRs authored by this person that were merged to the default branch in the last 90 days.	Baseline throughput indicator. Low counts combined with high WIP may signal blockers.
Reviews Given	Count of PR reviews submitted by this person in the last 90 days (all states: approved, changes requested, commented).	Identifies reviewers who carry a disproportionate load, and those who rarely review.
Avg Lead Time	Average time from the first commit on each PR to merge, across all PRs this person authored.	Compare against team median. High individual lead time may mean large PRs or slow code review.
Avg PR Size	Average lines changed (additions + deletions) per merged PR.	Smaller is usually better. Large average sizes increase review time and defect risk.
Review Response	Median time between a PR being opened and this person submitting their first review on that PR.	High values indicate a slow reviewer or reviewer overload.
First-Pass Approval Rate	Percentage of PRs this person authored that were approved on the first review round (no changes-requested cycle).	High rates indicate clear PR descriptions and well-scoped changes.
Self-Merges	PRs the author merged themselves without any other approver.	Occasional self-merges are fine (hotfixes). A high rate may indicate a lack of code review culture.
After-Hours Commits %	Percentage of commits made outside the organization's workday (default Asia/Saigon 08:00–19:00, set in Settings). Visible in the commit hour distribution chart on the contributor profile.	A proxy for burnout risk. A sustained high rate warrants a conversation about workload.

Reviewer Load Matrix

A heatmap where rows are PR authors and columns are reviewers. Each cell shows how many of that author's PRs were reviewed by that reviewer. Dark cells indicate a concentrated review relationship.

Signal	Meaning
One reviewer in nearly every row	Single-point-of-failure reviewer — a bottleneck and a bus-factor risk.
One author never reviewed by anyone	Possible self-merge pattern or team isolation — worth investigating.
Balanced matrix (many medium-shade cells)	Healthy cross-reviewing culture with distributed knowledge.

Bus Factor

The bus factor of a module is the minimum number of team members whose absence would severely impact the project. GitDash computes it per file-path prefix as the smallest number of authors who together made 80% of the module's commits.

Term	Definition
Bus factor	Smallest number of authors whose commits add up to at least 80% of a module's commits. A module is the first two path segments (one for files one level deep, (root) for top-level files).
Window	The last 90 days, at most 300 commits. A commit counts once per module it touches. Bot commits are counted.
Risk threshold	Bus factor 1 is critical, 2 is a warning, 3 or more is healthy.

Team Leaderboard Columns

Column	Calculation	What to look for
PRs Merged	Count of PRs authored by this person that were merged to the default branch in the last 90 days.	Baseline throughput indicator. Low counts combined with high WIP may signal blockers.
Reviews Given	Count of PR reviews submitted by this person in the last 90 days (all states: approved, changes requested, commented).	Identifies reviewers who carry a disproportionate load, and those who rarely review.
Avg Lead Time	Average time from the first commit on each PR to merge, across all PRs this person authored.	Compare against team median. High individual lead time may mean large PRs or slow code review.
Avg PR Size	Average lines changed (additions + deletions) per merged PR.	Smaller is usually better. Large average sizes increase review time and defect risk.
Review Response	Median time between a PR being opened and this person submitting their first review on that PR.	High values indicate a slow reviewer or reviewer overload.
First-Pass Approval Rate	Percentage of PRs this person authored that were approved on the first review round (no changes-requested cycle).	High rates indicate clear PR descriptions and well-scoped changes.
Self-Merges	PRs the author merged themselves without any other approver.	Occasional self-merges are fine (hotfixes). A high rate may indicate a lack of code review culture.
After-Hours Commits %	Percentage of commits made outside the organization's workday (default Asia/Saigon 08:00–19:00, set in Settings). Visible in the commit hour distribution chart on the contributor profile.	A proxy for burnout risk. A sustained high rate warrants a conversation about workload.

Reviewer Load Matrix

A heatmap where rows are PR authors and columns are reviewers. Each cell shows how many of that author's PRs were reviewed by that reviewer. Dark cells indicate a concentrated review relationship.

Signal	Meaning
One reviewer in nearly every row	Single-point-of-failure reviewer — a bottleneck and a bus-factor risk.
One author never reviewed by anyone	Possible self-merge pattern or team isolation — worth investigating.
Balanced matrix (many medium-shade cells)	Healthy cross-reviewing culture with distributed knowledge.

Bus Factor

Term	Definition
Bus factor	Smallest number of authors whose commits add up to at least 80% of a module's commits. A module is the first two path segments (one for files one level deep, (root) for top-level files).
Window	The last 90 days, at most 300 commits. A commit counts once per module it touches. Bot commits are counted.
Risk threshold	Bus factor 1 is critical, 2 is a warning, 3 or more is healthy.