GitHub Metrics

PR throughput, cycle time, code review workload, contributor leaderboards, commit activity (daily heatmap and weekly trend), a "Friday merges" trend so a team can track a stop-merging-into-prod- on-Fridays goal over time, and AI-assisted-code detection across recent pull requests.

Exclude-list, not include-list

Every real teammate and service account is shown by default; a manager opts specific accounts out (bots, other teams' members sharing a repo), instead of engineering metrics silently hiding anyone who forgot to fill in a profile field. This is a deliberate design choice — see the Product positioning for why it matters.

Attribution

A person's commits, pull requests and reviews are only attributed to them once their GitHub username is set on their roster/profile entry. A missing username is the single most common cause of "the metrics look wrong" — check that first.

Refresh & caching

Metrics refresh automatically every 15 minutes, with a manual force-refresh available. Treat these as activity counts, not a performance score: review load and PR size aren't comparable across people doing different kinds of work. The most useful signal is often review distribution — whether one person is reviewing everything.