GitHub published its 2026 Octoverse report on October 28, 2026, covering the 12 months ending September 30, 2026, across public and private repositories. The central finding is that the volume of code developers ship hit a new high, while agents have moved from an experiment to an everyday way of collaborating, with code review becoming the new center of gravity in how people and agents divide the work.
Three sets of numbers first
- 17.9 billion pushes, more than 2024 and 2025 combined; 34.3 billion commits, more than three times the total two years earlier; 1.3 billion merged pull requests, an average of 3.5 million a day.
- GitHub Actions ran 45.4 billion jobs over the year, an average of 1,440 per second; developers merged more than 30 million Dependabot pull requests, about double the 2025 pace.
- Public contributions reached 2.5 billion, more than double last year's total; the platform now serves more than 225 million developers, with the United States at 38.3 million and India at 32 million still the two largest communities.
The steepest curve in the report is how fast agents spread: pull requests started with an agent rose from 17% in March to more than 40% in September; among repositories created this year, those with an agent configuration file averaged eight times as many commits as new repositories without one; and in September, 61% of GitHub Copilot users used more than one model, with requests spread across general purpose, deep reasoning and planning, and fast and lightweight model types. Activity accelerated sharply around June, which GitHub attributes to stronger models, more mature orchestration tools, and agents that could track progress across days and run in the cloud.
What the numbers can and cannot show
Eight times as many commits is a correlation, not proof of causation: repositories set up agent-first from day one may well come from more skilled teams with clearer goals. Likewise, the report does not break down how much of the surge in commits is agent-generated code, or how much of it genuinely passed review. For developers, the more concrete change is where the work sits: starting tasks and reviewing results take a larger share, while writing code line by line takes a smaller one. Octoverse offers no answer on quality and maintenance cost; the question for the next phase is how much rework, months from now, the code merged in such a hurry will demand.
