Activity

GitHub activity, pulled live from aamoghS. Private repos show up only as a daily commit count.

How this works

A Vercel function renders this page with the feed already in it, and the page asks /api/github for updates every ten seconds. The goal is to show a push within seconds without spending GitHub’s rate limit while nothing is happening.

Every twenty seconds the server asks GitHub whether anything moved: my repo list, sorted by last push, and my public events. Both are conditional requests with an ETag, and when nothing changed GitHub answers 304, which does not count against the limit. Most checks cost nothing.

When a push lands, only the repos whose pushed_at changed are read again, with one GraphQL query each, in parallel. A query pulls my commits from the default branch and the five most recently updated branches, so feature-branch work shows before it is merged, and costs about one point. Every other repo comes from cache. The contribution calendar and the open source pull requests come from a second GraphQL query that refreshes every ten minutes.

A rebuild has seven seconds. Anything slower is cut off, the page renders with what arrived, and the next check fills the gap. If the remaining quota ever drops low, the server serves its cached copy until the limit resets.