GitHub logs 1.2 billion commits in a week, expands Copilot

GitHub's own numbers frame the shift: more than 1.2 billion commits in one week in October, over 400% more than a year earlier, and more than GitHub received in all of 2025. That volume is the backdrop for the company's argument that writing code is no longer the bottleneck. The friction has moved to the work around the code—gathering requirements, reviewing changes, and investigating what happens after a release.

The work is structured into four stages—Plan, Build, Verify, and Observe—and maps Copilot features to each. In planning, Copilot can pull scattered context from tools like Slack or Teams, create GitHub Issues, and use Plan Mode to compare approaches. In building, session continuity and cloud sandboxes let work continue across devices. In verification, stacked pull requests, Code Quality checks, and Copilot code review aim to make changes easier for humans to review. In observation, Copilot can connect to observability tools and business data to help investigate production issues.

The pitch is less about replacing developers than about letting them spend attention on decisions rather than retrieval and routine checks. GitHub's advice is to start with one frustrating piece of work and put an agent on it, then expand over time—a gradual adoption path rather than a wholesale process change.