Octoverse: Commits, pushes, reach new highs in 2026

See how a record year of growth reached every industry, every field, and every kind of builder in the 2026 Octoverse report.

24 minutes

Share:

Developers pushed code to GitHub 17.9 billion times in the past 12 months, more than in 2024 and 2025 combined.

Behind that number are developers building what interests them and what their communities need. In Nepal, one developer built a flood bulletin on GitHub Pages with verified information on roads, rescue, weather, and power. It has since grown into Gati, a Nepali-first relay of official disaster alerts that runs on GitHub Pages and Actions. Elsewhere, developers at NASA’s Jet Propulsion Laboratory are creating software designed to run programs aboard spacecraft, and fans built open-source firmware that lets people customize their e-readers. Curiosity, aimed in every direction, at a scale GitHub hasn’t seen before.

That growth happened quickly. Partway through the year, activity on GitHub bent sharply upward, just as agents went from something developers were trying out to something they were working alongside. Developers picked from more models than ever and built in industries we are highlighting in this report for the first time, from health care to agriculture.

Octoverse is our chance to step back and look at the whole picture. This year, that picture is bigger than ever. Here is what stood out most:

Underneath it all, AI models and the harnesses built around them have advanced over the past year, and developers have more to choose from. Growth is moving quickly: one year into last year’s five-year developer growth projections, every country we projected has already closed at least a fifth of its distance to 2030, and our own forecasting models no longer agree on where it will go next.

This year was all about momentum. Developers pushed code changes to GitHub 17.9 billion times in the past 12 months, more than 2024 and 2025 combined. Commits across all repo types (public and private) climbed even faster to 34.3 billion, more than three times where they stood two years ago. Merged pull requests more than tripled to 1.3 billion over the same period, an average of 3.5 million a day.

Agents were one of the tools developers leaned on hardest this year, pulling them deeper into daily work. Among repos created this year, the average repo with an agent configuration file logged eight times as many commits as the average new repo without one, sign that individuals and teams building with agents from day one are moving at a markedly different pace.

Developers also relied on automations to keep projects moving. GitHub Actions ran a job 1,440 times every second this year. This equals 124 million times a day and is more than three times last year’s total. Developers merged more than 30 million Dependabot pull requests to keep dependencies current and reduce the use of known vulnerabilities, about double 2025’s pace.

Our telemetry shows activity climbing steadily from January, then surging around June, as if developers everywhere saw new possibilities at once. Right around then, a cluster of industry-wide shifts landed: better underlying models, the harnesses and tools built around them, and the agents running on both. Agents moved from single-session tools to persistent ones that could track progress across days and orchestrate other specialized agents. Just as important, agents began making extensive use of the cloud, executing work remotely as well as on local machines.

This momentum is showing up both in brand-new repos and from developers who have been building for years. From June onwards, about 55% of all commits came from brand new repositories. But plenty more commits came from developers who’ve been around a while: developers who pushed code in the past 12 months have been on GitHub for an average of 36 months, and of those who opened a pull request in August, more than 75% pushed code in September. They are also branching out: the average developer now works across 10% more repositories than they did a year ago.

That staying power shows up in open source too. Public contributions soared to 2.5 billion in 2026, more than double last year’s total (1.12 billion). Behind those numbers are developers who keep showing up, like @kinlane, who made more than 1 million contributions across his public repositories using agentic workflows to keep a machine-readable catalog of public API information current. Another example is @kim-em, who made more than 178,000 contributions while maintaining mathlib, which is a community library of computer-checked mathematics. @andig, a maintainer of the open source EV charging controller and home energy management system evcc, contributed over 21,000 times.

These are just a few examples of the work millions of developers do every day. To all the developers doing work like this and beyond: we see you, and we’re glad you’re building.

Behind every number in this report is a developer. GitHub now serves more than 225 million of them, and the community is growing around the globe. The United States (38.3 million) and India (32 million) remain the two largest developer communities, and each added more than 10 million developers this year. Brazil added 3.28 million developers on GitHub this year, the third most of any country.

Last year, we projected that India would reach 57.5 million developers by 2030 and the United States 54.7 million. One year into that five-year window, every country in our projections has already closed at least a fifth of the distance to its own 2030 figure. The United States has closed 38.6%, and India 28.3%.

The same momentum shows up across regions, each with its own local context:

One year in, growth is strong against last year’s projection, and projecting the next five years is getting harder. We ran more than 40 forecasting models forward to 2031, time-series and regression models built on historical sign-up and usage data, each assuming a different pace of growth. About half call for “extreme” growth, with developer counts on GitHub more than tripling by 2031. Just under half call for “substantial” growth, doubling to tripling. Only three models expect anything close to modest, under 2x growth.

Forecasts are estimates, and a spread this wide shows how much the 2026 surge widened what is plausible by 2031. What holds steady is the shape of the trend: a developer community growing in more places at once.

In past reports, “everywhere” meant more developers and more countries, such as in the context of the top countries contributing code to public repositories:

This year, it also means more fields, including industries we haven’t measured before.

We’re sharing our view of public repositories by industry using the North American Industry Classification System (NAICS), which sorts economic activity into sectors. A language model classified random samples of public repositories created each year from 2022 to 2026, assigning each to the industry it serves based on its name, description, topics, and README. We also tracked two signals: whether a repository mentions AI, and whether an agent opened a pull request against it.

The two signals do not always move together. In administrative and support services, mining, health care, and agriculture, more than four in 10 repositories mention AI, yet agent-opened pull requests are rare, less than 3 percent. Construction breaks that pattern. About a quarter of its repositories mention AI, but about 9 percent have agent-opened pull requests, the highest share of any sector, with manufacturing next.

The same classification shows how each industry’s footprint has shifted since 2022, and sectors well beyond software are climbing. Professional, scientific, and technical services rose from fourth to second place among all industries, behind only information. Agriculture, forestry, fishing and hunting climbed two spots, and finance and insurance and health care and social assistance each moved up one. Against each sector’s own 2022 baseline, mining, quarrying, and oil and gas extraction grew roughly 65 times from a small starting base, administrative and support services and construction 17 to 18 times, and even manufacturing, the slowest of these, almost tripled.

Behind these sector shifts are people who know their fields, now using AI coding agents to build. For example, in manufacturing, a small team built a way to turn a photo of your tools into a custom-fit, 3D-printable drawer organizer. A research lab in health care made it easier for scientists to analyze huge digital scans of tissue samples, the kind pathologists study to understand disease. In Copenhagen, a university lab built a pipeline that classifies video of chickens at play, from frolicking to worm chasing. A University of Waikato energy center built a toolkit that helps industrial plants find heat they can reuse, and Bulgaria’s digital ministry open-sourced a portal where anyone can trace who won a public contract and for how much. For writers, a novelist built a free app that makes a manuscript look like a book as you type. In field after field, the people closest to the problem are building the solution, with agents helping along the way.

Professional, scientific, and technical services, which grew about 5 times over its own 2022 baseline and climbed to second place, is the work of researching, engineering, and advising, and open code has long been part of how that work gets done. In biochemistry, the work behind AlphaFold earned Demis Hassabis and John Jumper a share of the 2024 Nobel Prize in Chemistry. In computer science, Tensor2Tensor accompanied the paper that introduced the Transformer, the architecture behind today’s large language models, “Attention Is All You Need.” In medicine, sars-cov-2-stability held the code and data behind one of the earliest papers on how long the virus survives in the air and on surfaces. In physics, eht-imaging was one of two open-source libraries used to reconstruct the first image of a black hole. A repository has quietly become part of the paper trail behind published research.

More developers now begin a pull request by specifying what they want and orchestrating the agents that carry it out. By September 2026, more than 40% of pull requests on GitHub started with an agent’s first draft, up from 17% in March. That is 110 million in September alone, about 6x March’s volume.

Agent-started pull requests also more often change multiple files: about 87%, compared with 79% of pull requests without detected agent involvement. They are landing quickly too. In February, 83% of agent-involved pull requests merged within two weeks, a touch behind the roughly 86% for pull requests without detected agent involvement. By September, agent pull requests were at 90%, while the comparison group held at about 86%.

Among GitHub Copilot’s monthly active users, 55% now use agentic features, up from 35% a year ago. The steepest growth is in the most hands-off mode. Copilot cloud agent, where a developer assigns a task and an agent works on it independently, grew 230% year over year, against 85% for agent chat. Developers still ask agents questions, and increasingly they hand over whole tasks.

The willingness to delegate is reflected by the kinds of tasks developers are attempting. Public repositories mentioning interoperability or reverse engineering increased more than 300% year over year, from about 30,000 created in 2025 to more than 130,000 in 2026.

Review is where developers shape what comes back, and more tooling is being built for it. Stacked pull requests, which split related work into smaller changes that are easier to review in sequence, launched as a preview on July 30, and more than