GitHub employees what's going on? Why?

GitHub employees what's going on? Why?

77 pointsby sharts59 comments

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • GitHub Will Prioritize Migrating to Azure Over Feature Development - https://news.ycombinator.com/item?id=45517173 - October 2025 (63 comments)

    HN Search: azure capacity - https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

    Azure Capacity Crunch Extends into 2026 Amid Data Center Constraints - https://windowsforum.com/threads/azure-capacity-crunch-exten... - October 9th, 2025

    https://news.ycombinator.com/item?id=47427779

  • If you are doing 1000 commits a day, whats the point of git?

    Does the AI ever look back at the shit trail it left behind?

    Diffs are no longer diffs, they look like largescale delete and rewrite

  • AI definitely does look at git commit history in my experience
  • GitHub is struggling because it is owned by Microsoft.
  • AI + Microsoft = kabum
  • i guess its because of the new cursor platform
  • I think it's two things:

    - GitHub attempting (and seemingly failing) to move to Azure infrastucture for its website backend

    - AI generated code wrecking the site due to the volume of activities.

  • So you're asking github employees to violate their NDA?
  • Frankly yes. Do it in a way that doesn’t violate outright or cover your tracks. Customers deserve to know the truth of the type of company they are dealing with.
  • I got an "it is unacceptable" from their CPO on 8/7, and that they are "working around the clock on it".

    https://x.com/mariorod1/status/2085800861469495465

    I really think something deeper is going wrong there, and they're not being honest with their paying customers (and enterprises) about it.

  • Many microsoft services are down/failing today, including sites hosted on Azure. I'm guessing it's a larger MS outage.
  • So perhaps we should be asking Azure engineers, not Guthub engineers?
  • non-helpful answer: the "Microsoft Acquires GitHub" line in this graph answers all questions https://damrnelson.github.io/github-historical-uptime/
  • No one hates msft more than me, but there’s no way you think this one data point is useful to explain anything at all
  • Microsoft acquires GitHub and subsequently moves all infrastructure to Azure
  • On the other hand I think usage increased and GitHub operates now at a different scale.
  • Note that most of the downtime in that graph comes from Github Actions, which simply didn't exist before the Microsoft acquisition.

    The downtime also starts happening in 2020, which is a while after the acquisition. 2020 was the year many people started learning to code while being stuck at home.

  • Microsoft acquiring GitHub is not a valid root cause analysis explaining Github’s degraded SLA.
  • Github is struggling because AI-boosted coding increased the number of commits 14x in the past year, and the pace is still accelerating. The site is struggling to keep up. Github's COO confirms it here: https://x.com/kdaigle/status/2040164759836778878

    Platform activity is surging. There were 1 billion commits in 2025. As of three months ago, it was 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.)

    20% of all GitHub accounts were created in the past 6 months https://x.com/kdaigle/status/2082604368399159542

  • Are these disproportionately in the free tier? Or is the increased storage load similar across the paid tiers?

    Might be worth considering a /GB/MO fee. Let's face it, VCS is a (glorified) storage service.

  • I think that data is a bit dated and misleading, but I would love to see if AI slop is a contributing factor here once the dust settles and how Github will address it. Looking at the return to mean in https://areyougoingexponential.rhys.dev/kdaigle makes me think the COO spike could be a Karpathy wiki or an agent too.
  • Nobody at Microsoft could've predicted AI was going to be so popular!
    by pluc
  • Github is owned by Microsoft, its not like its some boostrapped startup who has a closet of servers that are melting.
  • My sense is that a lot of this activity isn't even legitimate use. As one example: my company has a GitHub app, and last night some bot added my app to 1700 repos. Then the bot immediately started rapid-firing commits which each affected hundreds of files, triggering a deluge of GitHub webhooks to my servers.

    The repo names all matched other GitHub apps, so my sense is this bot had added 1700 GitHub apps to 1700 repos, with that number rapidly increasing at the upper bound of whatever GitHub's rate limit is.

    My systems caught it quickly and auto-booted the bot, but the whole situation is ridiculous.

  • > Github is struggling because AI-boosted coding increased the number of commits 14x in the past year, and the pace is still accelerating.

    Sure, but how is OpenAI, and Claude handling the increased usage? They are handling it a lot better than Github. Just because you have fast growth does not mean you can not handle it.

    Instead you have to realize that you are entering into a high growth phase and design around that.

    It has been clear that we are in a high growth phase for around a year now and Github still hasn't adapted to that properly.

    At some point you have to admit that Github ready for the moment.

  • The obvious answer is to end free unlimited private repos. Source is no longer a specific thing. GitHub is just a free S3 or Azure provider.
  • I would take what C-level execs say with a grain of salt. Remember these folks hire people with plenty of system design experience. They likely also have the money for hardware resources.

    If load was an issue these things would have been solved already. Or they are purposely causing millions of dollars of productivity loss daily by not solving this.

    Something more serious is at play. And I want to hear from the actual underlings.