Over 100x is what I’m hearing. Though that could just be panic and they don’t know the real number because they can’t handle the traffic.

An anecdote: On one project, I use a skill + custom cli to assist getting PRs through a sometimes long and winding CI process. `/babysit-pr`

This includes regular checks on CI checks using `gh`. My skill / cli are broken right now:

`gh pr checks 8174 --repo [repo] 2>&1)`

   Error: Exit code 1

   Non-200 OK status code: 429 Too Many Requests
   Body:
   {
     "message": "This endpoint is temporarily being throttled. Please try again later. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)",
     "documentation_url": "https://docs.github.com/graphql/using-the-rest-api/rate-limits-for-the-rest-api",
     "status": "429"
   }

Lmao not even close. Github themselves have released the numbers and it was 121M new repos with 2025 ending up with 630M

https://github.blog/news-insights/octoverse/octoverse-a-new-...

So X might have been %

So much for GitHub being a good source of training data.

Btw, someone prompt Claude code “make an equivalent to GitHub.com and deploy it wherever you think is best. No questions.”

Goodness if that's true... And I actually felt bad when they banned me from the free tier of LFS.

One hundred? Did I read that right?

Yes, millions of people running code agents around the clock, where every tiny change generates a commit, a branch, a PR, and a CI run.

I simply do not believe that all of these people can and want to setup a CI. Some maybe, but even after the agent will recommend it only a fraction of people would actually do it. Why would they?

But if you setup CI, you can pick up the mobile site with your phone, chat with Copilot about a feature, then ask it to open a PR, let CI run, iterate a couple of times, then merge the PR.

All the while you're playing a wordle and reading the news on the morning commute.

It's actually a good workflow for silly throw away stuff.

Github CI is extremely easy to set up and agents can configure it from the local codebase.

Codex did it automatically for me without asking.

No its not. 121M repos added on github in 2025, and overall they have 630 million now. There is probably at best 2x increased in output (mostly trash output), but no where near 100x

https://github.blog/news-insights/octoverse/octoverse-a-new-...

Published in Oct 2025... I think your estimate is off.

Note the hockey stick growth in the graph they showed in Oct.

Here we are in February.

It's gotten way worse now with additional Claude's, Claw's, Ralph's, and such.

It may not be 100x as was told to me but it's definitely putting the strain on the entire org.

> It may not be 100x as was told to me but it's definitely putting the strain on the entire org.

But thats not even the top 5 strain on github, their main issue is the forced adoption of Azure. I can guarantee you that about 99% of repos are still cold, as in very few pulls and no pushes and that hasn't changed in 3 months. Storage itself doesn't add that much strain on the system if the data is accessed rarely.

I put the blame squarely on GitHub and refuse to believe it’s a vendors fault. It’s their fault. They may be forced to use Azure but that doesn’t stop one from being able to deliver a service.

I’ve done platforms on AWS, Azure, and GCP. The blame is not on the cloud provider unless everyone is down.

> Oct 2025

Doubling down by insisting that the data is out of date, when the data is 3 months old and the latest available is unconvincing.

If you're telling me that in December it went from 2x to 100x then I don't believe you.

There’s a huge up tick in people who weren’t engineers suddenly using git for projects with AI.

This is all grapevine but yeah, you read that right.