GitHub contribution metrics, explained

What the numbers on a commit-history.com profile actually mean: commits, pull requests, reviews, repositories, and private contributions — in detail.

• What GitHub commit counts actually measure

  How GitHub decides which commits count — default branches, linked emails, squash merges, forks — and what a big commit count does and doesn't tell you.

• What a GitHub pull-request count means

  GitHub counts pull requests you open, not ones that get merged. What PR counts reveal about how a developer collaborates across repositories.

• What a GitHub issue count says about a developer

  GitHub counts issues you open. Why high issue counts belong to maintainers, testers, and power users — and why zero issues isn't zero contribution.

• Pull-request reviews: GitHub's most invisible work, counted

  GitHub counts every pull-request review you submit. Why review counts surface senior engineers whose commit graphs look quiet.

• What a high repository count means on GitHub

  GitHub counts repositories you create — forks don't count. Why this differs from the profile page number, and what a high repo count signals.

• What “private contributions” means on GitHub

  Why some GitHub profiles show thousands of private contributions and others show none — the opt-in setting, what the count includes, how we track it.

• How “Total contributions” is calculated

  How Total sums commits, issues, PRs, reviews, repos created, and private contributions into one lifetime number — the exact recipe and its caveats.

• What GitHub follower counts mean (and don't)

  Followers measure reach, not contribution. Why follower counts and commit counts tell independent stories, and how the followers leaderboard works.