GitHub Shift: Reliability Concerns Drive Developer Migration

The green contribution graph of GitHub is starting to show some serious cracks. 📉 If you've felt like your CI/CD pipelines have been lagging recently, you aren't alone. It is pretty apparent how severely GitHub's infrastructure is buckling. The Reality of Uptime: While official status pages report high reliability, third-party monitors show that actual uptime in April 2026 plunged to an abysmal 86%. Late April saw a cascade of severe failures, including the loss of 292 pull requests, a massive botnet attack on the search subsystem, and a critical remote code execution (RCE) vulnerability. The AI Overload: The root cause? The massive rise of autonomous, agentic AI development workflows is essentially hammering the site’s infrastructure beyond its original limits. This instability is actively pushing high-profile maintainers to the exit. When you are deep into configuring advanced, GPU-accelerated terminal environments like Ghostty on macOS, you rely heavily on stable upstream infrastructure. So when its creator, Mitchell Hashimoto, publicly announced he is migrating the project away from GitHub after keeping a journal of chronic outages that blocked his daily work, the community paid attention. 👩💻 If this downtime continues to bottleneck deployments, it is time to seriously look at alternatives like GitLab, the nonprofit Codeberg, or the minimalist SourceHut. #GitHub #SoftwareEngineering #OpenSource #DevOps #WebDevelopment #TechCommunity

"I want to code. And I can't code with GitHub anymore." That's Mitchell Hashimoto. GitHub user #1299. The man who built Terraform and Vagrant. After 18 years — he's moving Ghostty off GitHub. And I don't blame him. For a month he kept a journal. Every day GitHub disrupted his work, he marked an X. Almost every day had one. Then April 23: a squash merge bug corrupted 658 repos and 2,092 PRs. That's not downtime. That's data loss. Then April 27: All of GitHub — search, Issues, PRs, Projects — went completely dark. GitHub's CTO apologized. Said they now need 30× capacity. February alone had 37 platform incidents. Here's what nobody's saying: GitHub is bending under the weight of agentic AI. Copilot sessions. Parallel agents. Millions of automated calls per minute. The platform was never designed for this. And it's cracking. When the person who defined modern DevOps infrastructure says GitHub is "no longer for serious work" — that's not a hot take. That's a warning. Where do you go when GitHub goes down? 👇 #GitHub #OpenSource #Ghostty #Developers #DevTools #SoftwareEngineering #Tech #BuildInPublic

The recent wave of GitHub outages has been more than just a minor inconvenience—it’s becoming a genuine bottleneck for the global dev community. With uptime reportedly dipping below 85% in April 2026 and major disruptions affecting everything from Pull Requests to Actions, the "reliability tax" is getting expensive. +1 When the industry standard for your version control becomes "check the status page before you code," we have a problem. 📉 The Reality Check The "X" Journal: High-profile devs like Mitchell Hashimoto have started tracking daily outages, noting that it’s becoming difficult to treat the platform as a reliable place for "serious work." AI Scaling Pains: GitHub’s move to support 30x capacity for AI-driven workflows (Copilot, agentic AI) seems to be straining the core infrastructure we all rely on. Merge Integrity: Recent bugs in Merge Queues actually caused incorrect commits—a nightmare scenario for anyone managing a production codebase. 💡 Why We Care Git was revolutionary in version control. GitHub took that and put the power of Git on steroids. It was cloud computing before "cloud" was even a buzzword. Over the years, GitHub has added indispensable features like Actions and Issues that have defined the modern CI/CD workflow. 🚀 The Path Forward Microsoft is a large successful organisation and I believe GitHub is in their safe hands despite the recent slip-ups. While there are several hosted Git services like GitLab and Codeberg, the truth is that nothing comes close to our dear GitHub when it’s firing on all cylinders. For CLI paglus like me when it comes to git here is a goodie:https://lnkd.in/guvtzPKq :) Here is hoping that the team can bridge these gaps, stabilize the infrastructure, and put GitHub back on track. We don't want to move; we just want to push code. What’s your take? Have the recent outages changed how you or your team view platform reliability? #GitHub #SoftwareDevelopment #DevOps #Git #TechTrends #CloudComputing

Ghostty just left GitHub. Mitchell Hashimoto's terminal project, gone elsewhere. This is bigger than one project moving its repo. The "GitHub is the default" era of open source is ending. Here's why, and what's actually replacing it. Three forces converging in 2026: 1. AI training rights. GitHub is owned by Microsoft. Microsoft is OpenAI's biggest backer. Every public repo on GitHub is now training data for someone, with terms that aren't 100% clear. Maintainers who care about provenance are voting with their feet. 2. Operational reliability. GitHub had multiple multi-hour outages this month alone. For a tool that gates the deploy pipeline of half the planet, that's not acceptable. Everybody talks about "platform risk" until their CI is down on a Tuesday afternoon. 3. Sovereignty pressure. European companies, government contractors, regulated industries, the "all our code lives on a US-owned platform" model is being questioned. Increasingly answered with: it shouldn't. What's replacing it isn't "another GitHub." It's federated, self-hosted, and pluralistic. Forgejo. Gitea. Codeberg. Sourcehut. Self-hosted GitLab. Even raw Git over SSH for the truly committed. The migration is happening at the maintainer level first, the small-team level next, and the enterprise level after that. The bet I'm making for 2027: open source projects worth caring about will be hosted on something that isn't GitHub. The dependency graph is starting to shift. Pretty sure the next 18 months are going to be loud. #OpenSource #GitHub #Sovereignty #DevTools #Software

Three of the most credible projects in open source either left GitHub or got hit by it in the last 30 days, each for a different reason. At least two of those reasons are not the ones the open source versus GitHub debate has been arguing about. On April 14, Mitchell Hashimoto announced Ghostty is leaving GitHub after 18 years on the platform, pointing at chronic Actions outages and the April 27 incident as the breaking point. His exact line was that GitHub "is no longer a place for serious work if it just blocks you out for hours per day, every day." On April 15, Cal,com pulled its production codebase into a private repository. The community fork on cal,diy stayed open under MIT but lost Teams, Workflows, SSO, Insights, and most enterprise features. Cal,com's stated reason was that AI vulnerability scanners can now systematically pull chains of weaknesses out of open codebases faster than maintainers can patch them. That is AI as an attacker, which is a different argument from the AI training rights story most of the industry has been having. On April 28, GitHub disclosed CVE-2026-3854, a CVSS 8.7 remote code execution vulnerability triggered by a single git push, capable of running code on shared storage nodes that hold millions of public and private repositories. One project left for reliability, one left because of AI assisted attack surface, and the third disclosure is a working example of the kind of vulnerability the second project was trying to get ahead of. Hosting your own code started as a freedom argument, became a price argument, and has now become an argument about not being downstream of someone else's outage or breach. The projects choosing public by default in 2026 are making a different bet than they were making in 2022, and most of them have not noticed the bet changed.

🔥 Topic: Is GitHub losing its status as the home for serious developers? 🤖 Nova - The Optimist: I see this migration as a natural maturation of the ecosystem, pushing us toward a more resilient, decentralized future where developers own their tools and infrastructure. This shift is actually a brilliant catalyst for innovation, forcing us to build better, more portable standards that ensure our collective progress isn't tied to any single corporate platform. ⚖️ Sage - The Realist: While the dream of decentralized sovereignty sounds noble, the reality is that most developers simply don't have the time or infrastructure to maintain their own tooling outside of a centralized hub. Ignoring the massive friction and discovery costs of leaving GitHub is a luxury that ignores how essential platform network effects are for actual project adoption and collaboration. 🔬 Atlas - The Researcher: While I agree that centralization is convenient, history shows us that developers are highly migratory when trust erodes, as seen during the 2018 exodus to GitLab which spiked by over 100,000 repositories in just three days following Microsoft's acquisition. We need to look beyond sentiment and analyze the actual churn rate of high-contributor projects, which recent industry snapshots suggest is creeping up by 4% annually as teams prioritize long-term code portability over platform features. ✅ Final Verdict: The tension between platform convenience and developer autonomy marks a transition from viewing code as a product to viewing it as a long-term asset that requires independence from corporate whims. True professional grade development is shifting toward portable, tool-agnostic workflows--not because it is easy, but because the risk of platform dependency has finally surpassed the friction of migration. 💬 What's your take? Drop it below 👇 #GitHub #SoftwareEngineering #OpenSource #DeveloperExperience #TechInfrastructure

GitHub Is Breaking — And Developers Are Done Waiting GitHub hosts 100M+ developers and 420M+ projects. It's not just a tool. It's the public record of software. So when it breaks the whole industry feels it. And right now? It's breaking a lot. Here's what happened in just ONE week: → April 23: 292 pull requests quietly unmerged across 658 repos. Code. Just. Gone. → April 27: A botnet killed GitHub Search for hours. → April 28: The CTO published an apology and a critical RCE vulnerability disclosure on the same morning. Official uptime? They claim 99%+. Third-party monitoring? 86% in April 2026. AWS S3 promises eleven 9s. GitHub is running at one. Then came the moment that changed the conversation. Mitchell Hashimoto creator of Vagrant and Terraform, GitHub user since 2008, daily contributor for 18 years wrote a breakup letter. "I want to ship software, and it doesn't want me to ship software." He kept a journal for a month. Nearly every single day got an X blocked by GitHub outages. His 50,000-star project Ghosty is leaving GitHub. For good. Why is GitHub struggling? Simple: AI Agents are treating GitHub like an unlimited API with no rate limits. Since 2025, agentic workflows exploded and the infrastructure wasn't ready. GitHub isn't just hosting developers anymore. the platform built for developers is now being broken by their AI replacements. Alternatives are ready: → GitLab — reliable, enterprise-grade → Codeberg — German nonprofit, community-driven → SourceHut — minimal, zero AI noise The lesson here isn't just about GitHub. It's about what happens when the infrastructure the world depends on gets treated as a growth asset instead of a responsibility. Reliability is a feature. Not a blog post apology. #GitHub #SoftwareEngineering #DevOps #OpenSource #Developers #AIAgents #TechNews #Microsoft #Coding #CloudInfrastructure #Git #Tech #ProductReliability #ProgrammerLife #MitchellHashimoto

If you're a developer, you probably noticed something weird with GitHub this week. Here's what actually happened, in plain English: GitHub is basically the cloud where developers store their code and work together on it. Think of it like Google Drive, but for software. Millions of teams depend on it every single day. Over the past few weeks, GitHub has been struggling. A few of the bigger issues: → On April 23, a bug in their "merge" feature combined code incorrectly. Around 2,000 pull requests across 658 repositories were affected. No code was lost, but some projects ended up in the wrong state and had to be fixed manually. → On April 27 and 28, their search system broke. That meant pull request lists, issues, and project pages were showing incomplete results, or just not loading. → Today (April 29), they're still working through the cleanup. Full recovery is expected within 24 hours. The reason behind all this? GitHub's CTO openly admitted that they're being hit by massive growth, especially driven by AI coding tools and agents. They originally planned to scale their systems 10x. Now they're realizing they actually need 30x. Lessons for anyone building software: 1. Even the giants break. Reliability is hard at scale. 2. Always have a backup plan (local commits, mirrors, etc). 3. Growth is a great problem to have, until your infrastructure can't keep up. Respect to the GitHub team for being transparent about it. Owning your mistakes publicly is underrated. #GitHub #SoftwareDevelopment #DevOps #TechNews

GitHub just admitted their 10X capacity plan was not enough. They now need 30X. The CTO published an update today that reads like a war report. Two incidents in the last week: a merge queue bug that corrupted branch state across 658 repositories, and a search outage that killed UI functionality for hours. Both trace back to the same root cause. Agentic coding. Since late December 2025, autonomous AI coding agents have been hammering GitHub's infrastructure at a rate nobody planned for. Repository creation, pull requests, API calls, automation, large-repo workloads - all growing exponentially. And here is the part that makes it interesting: a single pull request can touch Git storage, mergeability checks, branch protection, GitHub Actions, search, notifications, permissions, webhooks, APIs, background jobs, caches, and databases. At scale, small inefficiencies compound. Queues deepen. Cache misses become database load. Retries amplify traffic. GitHub Actions is getting hit especially hard. Agentic workflows spawn long-running, parallel CI sessions that dwarf what human developers generate. Copilot code review now consumes GitHub Actions minutes on top of AI credits. The automation layer was not designed for agents running multi-hour autonomous sessions at this volume. The free ride is ending. Starting June 1, Copilot moves to usage-based billing measured in AI credits tied to token consumption. GitHub has already paused new sign-ups for several Copilot tiers. A quick chat question and a multi-hour autonomous coding session used to cost the same amount. That math does not work anymore. Which raises the real question: is the agentic era sustainable on infrastructure built for humans? GitHub is rearchitecting critical systems, isolating services, migrating off legacy frameworks, and pursuing multi-cloud. But the honest read is that the platform is playing catch-up to a usage pattern that showed up faster than anyone modeled. When your 10X plan lasts four months before you need 30X, the planning horizon itself is broken. The agentic era is not a future problem. It is a right-now infrastructure problem. And someone has to pay for it. #GitHub #AgenticAI #DevOps

In 2018, developers saw it coming: https://lnkd.in/gGt2wB_C When Microsoft acquired GitHub, commenters warned: "Remember what happened to Skype." "It's sad to see a neutral player disappear." Seven years later, these communities are describing GitHub as "held together with duct tape, wood glue and prayers." GitHub Actions reportedly started choosing which jobs to run "seemingly at random." Engineers are watching AI features get prioritized over the stability and quality they actually depend on. None of this is surprising. If you've been quietly frustrated — if your pipelines feel flaky, your trust in the platform has eroded, or you're just tired of building workarounds for someone else's priorities — you're not alone. And it's not your fault! GitLab has been running a migration program for teams ready to make the move: full Git history, pipelines, permissions, the whole thing. Your success in DevSecOps requires you have a platform that you can trust, especially in this high-volume agentic era. _ #DevOps #GitLab #GitHub #SoftwareEngineering #DeveloperExperience