Skip to content
Buse Turgay Sönmez

Design Engineer, Belgrade

Counting my own commits

I wanted a contribution grid that shows volume, so I built one from my own git history instead of using GitHub's. The first count came to 3781 commits. The honest number was 1961. Most of the gap was other people's work, and the rest was the same history counted more than once.

W38

Scanning a working disk overcounts in two ways. Client repositories hold colleagues' commits, so the scan now matches my own addresses only. That took 3781 to 2255. The same history also lives on disk several times: four checked-out branches of one repository, a v1 and a v2 of one site. Keying every commit by its hash took 2255 to 1961.

GitHub's grid was never going to work. Its darkest square means four or more, so a day of 182 commits looks like a day of 4. My repositories are private, so the profile looks empty. Opening them would publish repository names that carry client names.

The window starts on 7 July because that is when most of these repositories were set up again, not when the work started. It covers eleven weeks, and it is not a career.

The grid does not count lines I typed either. Agents wrote most of this code. What it records is the days when something was decided, reviewed and shipped.

On stage

Shipping RecordData · Open the piece
--ground
oklch(0.985 0.003 85)
--surface
oklch(0.958 0.005 85)
--raised
oklch(1 0 0)
--ink
oklch(0.2 0.006 85)
--muted
oklch(0.43 0.008 85)
--faint
oklch(0.5 0.008 85)
--line
oklch(0.9 0.004 85)
--line-strong
oklch(0.6 0.006 85)
--accent
oklch(0.66 0.22 38)
--accent-ink
oklch(0.52 0.19 38)
--stage
oklch(0.152 0.004 85)
--radius-stage
36px
--radius-stage-sm
28px
--radius-media
24px
--radius-panel
16px
--radius-field
10px
--ease-out-expo
cubic-bezier(0.16, 1, 0.3, 1)

This week · W39One WebGL context, three leaksGeometry · 2026