Notes

My GitHub said I shipped nothing this year

The contribution graph showed 13. The real number was 16,931. What happened in between says a lot about how building works now.

3 min read Jul 4, 2026·Updated Jul 20, 2026

This week I rebuilt my personal site, and the template came with a GitHub contribution graph baked into the homepage. Mine rendered almost completely gray: 13 contributions in the past 365 days.

Thirteen. In a year where I shipped a tournament platform, an operating system for our athletic department's data, a Hall of Fame archive, a fan feedback tool, a family logistics app, and a coaching intelligence system for my son's 9U baseball team.

So we dug in. The real number turned out to be 16,931 - and the gap between 13 and 16,931 is a pretty good picture of how building software actually works in 2026.

Where the commits went#

Three things were happening at once:

1. Everything I build is private. My repos are tools for my department, my family, and my tournament - not open source. GitHub hides private activity from your profile by default, even from your own API queries, until you flip a single setting: Include private contributions on my profile. One checkbox. The graph recalculated the entire year on the spot.

2. My AI tools commit as themselves. About 9,400 commits in my repos this year are authored by lovable-dev[bot] - Lovable's agent pushing code it wrote at my direction. GitHub credits the bot, not me. Those commits will never show on my graph, and honestly, that's a fair philosophical call by GitHub. The bot typed. I decided.

3. My own commits were real - and invisible. Underneath the bot noise were about 3,800 commits authored by me, with my name and my email, on default branches of repos I own. My wiffle ball tournament platform alone had 1,778 of them. All hidden behind that one profile setting.

The interesting part#

The fix was trivial. The question it raises isn't: what should a contribution graph even measure now?

When I build with Lovable or Base44, the agent writes most of the code and commits under its own name. When I work in Claude Code, the commits carry my name because the work happens in my working tree. Same person, same decisions, same shipped product - completely different paper trail.

The graph was never really measuring "work." It was measuring a specific kind of work, done a specific way, in public. That was always a rough proxy, and AI agents have now broken it in both directions: builders look idle while shipping constantly, and I'd bet some graphs look busy with work nobody meaningfully directed.

I don't have a grand fix. But if you're hiring, evaluating, or just judging yourself by the green squares: the squares are lying to you now, in both directions. Ask what got shipped instead.

If your graph looks emptier than your year#

Two minutes of housekeeping:

  1. Flip the setting. GitHub → Settings → Profile → Include private contributions on my profile. Viewers see activity counts, never repo names or code.
  2. Check who's authoring your commits. If your AI tooling pushes to GitHub for you, look at the commit author on a few recent commits. If it's a bot identity, that work will never count as yours - decide whether you care.
  3. Commit under your own identity where it's yours. Work done in your own working tree, with your git config, counts - private or not.

My graph went from a gray wasteland to 16,931 overnight. Nothing about the year changed. Only the accounting did.

Share
Vote0