A new workload is stressing the write path

GitHub says developers and agents made 7.38 billion commits on the platform in September, more than five times the figure from a year earlier. Monthly Git activity grew from 218.2 billion events to 473.3 billion between September 2025 and August 2026, according to the company.

The change is not just more people cloning repositories. Agents can checkpoint after many small actions, push from separate branches and trigger CI or code scanning. A single push may fan out into many reads, and merges still have to converge onto shared branches while preserving Git’s consistency rules.

Why more caches are not enough

GitHub says monthly pushes rose from 0.69 billion to 3.35 billion, while pull-request merges approached four times their prior volume. GitHub Actions ran 3.26 billion times in September, over four times as many as a year before. These are company-reported platform totals, and the company attributes the architectural demands partly to agentic development.

Read scaling can often add caches and replicas. Writes are harder: each push has to be durably stored and made visible consistently before another agent or CI job builds on it. More replicas can increase write coordination, so the design must change how it handles concurrency rather than only adding read capacity.

The infrastructure story behind agents

GitHub says it is rebuilding parts of its Git architecture while the service keeps running. The company describes an approach that minimizes coordination where Git semantics do not require it, allowing more work to proceed independently while retaining correctness.

This is an enabling story rather than a new agent feature. If agents are going to make many small, parallel code changes, repositories and build systems have to absorb the write load without turning commits, merge queues or tests into a bottleneck. The reported volume provides a concrete signal of why core developer infrastructure is changing.

Explore the original source ↗

Source published October 6, 2026. Coverage is based on the maker’s announcement and demonstration.