A fair start line for public GitHub activity.

GitRacer asks GitHub for the same daily totals behind each profile’s contribution graph, then puts every racer on a cumulative line that starts at zero for the selected period.

What counts

We use GitHub’s GraphQL contributionCalendar. That can include qualifying commits, pull requests, issues, and pull request reviews. We do not reconstruct activity from repositories or scrape profile HTML.

What “starts at zero” means

If you choose 2026, every line begins at zero on January 1, 2026 and accumulates the contribution count for each actual calendar day. “Last 30 days” and “last 365 days” work the same way from their respective first dates. Lifetime begins at the earliest contribution year GitHub reports for anyone in the race.

Public and private work

Public contributions are visible. Private contributions only affect the graph when a GitHub user has enabled the profile option that exposes anonymized private contribution counts. GitRacer cannot see private repository names or content.

Cache and refresh rules

Completed calendar years are immutable in our cache. The current year refreshes automatically on the first view of a new UTC day. A manual refresh appears after three hours. Profiles and year blocks are shared across every race, so adding the same person elsewhere does not trigger duplicate work.

Known limitations

GitHub decides which activity qualifies, and profile settings can change the visible total. Account renames, deleted activity, delayed GitHub processing, or a privacy-setting change can temporarily make GitRacer differ from what a person expects.