GitHub's decline: Devs frustrated with flaky pipelines, prioritization

GitHub isn’t collapsing, but the shift in developer thinking is very real. This week, Mitchell Hashimoto, creator of Ghostty and HashiCorp co-founder, announced that after nearly two decades on the platform, his major project is moving away from GitHub. The deciding factor? Reliability. Frequent outages, particularly with GitHub Actions, have been disrupting consistent development and deployment workflows. Instead of treating it as occasional inconvenience, he’s taking structured action: Gradual migration to alternatives Keeping a read-only mirror on GitHub Exploring both open-source and commercial platforms This isn’t an isolated reaction. It highlights three growing concerns among engineering teams: • Reliability is now table stakes, not a nice-to-have. When your CI/CD pipeline stalls, velocity drops across the board. • Single-platform dependency carries real risk in 2026. • Flexibility and control are becoming non-negotiable. Many teams are now actively evaluating GitLab, Gitea, Forgejo, and other self-hosted or hybrid solutions. My take as a Full Stack & AI Engineer: Convenience got us here, but production-grade systems demand stability. Whether I’m building distributed backend services with FastAPI + Redis queues or integrating LLM workflows, I can’t afford tooling that blocks progress daily. The future belongs to platforms (and engineers) that prioritize control, observability, and resilience over ecosystem lock-in. Question for the community: If GitHub reliability continues to impact your workflows, would you consider migrating critical projects? What alternatives are you watching? #GitHub #DevOps #SoftwareEngineering #CI_CD #OpenSource #TechTrends #DeveloperExperience

A lot of developers rely on GitHub every single day, but the moment you ask them how it truly differs from GitLab, the answers often get blurry. And honestly, I understand why, on la surface they look similar, yet they don’t serve the same vision at all. GitHub has become the place where the world writes code together. Backed by Microsoft and fueled by a massive open-source community, it’s built for speed, simplicity, and collaboration. Actions, Codespaces, Dependabot… everything is designed to help teams move quickly and stay focused on building. GitLab, on the other hand, follows a completely different philosophy. It’s not just a code platform, it’s a full DevSecOps environment. CI/CD is built-in, security tools are native, governance is centralized, and you can even self-host it with the open-source edition. Many companies choose it because they want one platform to manage everything from planning to deployment. So the question isn’t really “which one is better?”. It’s more like “which vision matches the way you work?”. One focuses on velocity and massive adoption. The other focuses on deep integration and full end-to-end control. If you’ve used either platform in your projects, I’d really love to hear your experience. What actually makes a difference in your daily workflow? And what would you pick again if you had to start from scratch? Your insights will definitely help others who are still trying to choose the right tool. #GitHub #GitLab #DevOps #DevSecOps

"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 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

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

Even the giants have "off" days: Lessons from GitHub’s Merge Queue regression. GitHub recently confirmed a bug where roughly 2,800 pull requests were merged from the wrong base state, unintentionally reverting previous changes. While 0.07% sounds small, in production, "small" percentages can mean major downtime. Key Takeaways for Teams: 1)Automated Testing is King: GitHub is already expanding test coverage for merge operations. 2)Trust, but Verify: Always keep an eye on your branch history after a merge, especially when using automated queues. 3)Transparency Wins: Kudos to Kyle Daigle and the GitHub team for the quick RCA (Root Cause Analysis) and direct outreach to affected users. Have you ever encountered a "silent revert" in your workflow? How does your team guard against tool-level regressions? #GitHub #DevOps #SoftwareEngineering #CI/CD #TechNews

Your code freeze policy is a Slack message with a snowflake emoji. That's it. That's the whole enforcement mechanism. Someone posts "CODE FREEZE" in #engineering. Three people react. Then 10 minutes later, a PR gets merged anyway. "I didn't see it." We built NoShip to fix this. It's a GitHub App that actually enforces freezes -- blocked merges, blocked deployments -- and you control it all from Slack. DM the bot: "freeze all repos Friday 5pm to Monday 9am" Done. PRs show a failing status check. Deploys are gated. No one can "not see it." Need an emergency hotfix? Request an override in Slack. Admin approves with one tap. One-time bypass. Fully audited. Your Slack is already where freezes get announced. Now it's where they get enforced. Free to start at noship.io #DevOps #GitHub #CodeFreeze #Slack #SRE #PlatformEngineering #DeploymentSafety #EngineeringLeadership #SlackIntegration

🚨 Issues with #GitHub today? We’re seeing instability across the platform: ❌ Push & pull delays ❌ Pull Requests not loading ❌ Actions (CI/CD) failing or stuck ❌ Overall slow performance This is not a local issue — it’s affecting multiple environments. 💡 What I did (and what I recommend): I moved to running my own Git server using Gitea Open Source — and honestly, this is something more teams should consider. https://git.xdeye.com/ 👉 Here’s the practical advice: ✔️ Keep a self-hosted Git backup (Gitea / GitLab / bare repo). ✔️ Push your code to multiple remotes (GitHub + your own server). ✔️ Don’t depend fully on GitHub Actions — have manual or server-based deployment ready. ✔️ Keep production deployment independent from third-party outages. ✔️ Automate locally or on your own server where possible. Now my workflow is: Local → self-hosted Git → live servers GitHub is secondary, not critical ⚠️ With the growing use of AI tools and third-party automation inside CI/CD pipelines, complexity and risk are increasing. When one piece fails, everything can break. Better to stay in control. How are you handling redundancy in your Git workflow? #GitHub #DevOps #SelfHosted #Gitea #CI #CD #Security #ITInfrastructure

GitHub’s recent incident is every engineer’s nightmare: ✅ CI passed ✅ PR approved ✅ Merge successful …and the wrong code still landed in main. On April 23, GitHub confirmed that a merge queue issue affected 2,092 pull requests across 658 repositories, producing incorrect commits and silently reverting code in some cases. Good reminder that “all checks passed” doesn’t always mean “everything is correct”. #GitHub #SoftwareEngineering #DevOps #CodingLife

𝗬𝗼𝘂 𝗵𝗶𝗿𝗲𝗱 𝗮 𝗳𝘂𝗹𝗹-𝘁𝗶𝗺𝗲 𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗴𝘂𝗮𝗿𝗱 𝘁𝗼 𝗰𝗵𝗲𝗰𝗸 𝗶𝗳 𝘆𝗼𝘂𝗿 𝗳𝗿𝗼𝗻𝘁 𝗱𝗼𝗼𝗿 𝗶𝘀 𝗹𝗼𝗰𝗸𝗲𝗱. Every. Single. Night. That's Jenkins. 🏠 𝗧𝗛𝗘 𝗦𝗧𝗢𝗥𝗬 Jenkins is like owning a house with a dedicated security system — powerful, fully customizable, but 𝘆𝗼𝘂 maintain everything. The server. The plugins. The updates. The "why did it break at 2am" investigations. GitHub Actions is like moving into a modern apartment building where security is just... included. No basement server to babysit. Your workflow file lives right next to your code. Push a commit, the pipeline wakes up. Done. ⚙️ 𝗧𝗛𝗘 𝗟𝗘𝗦𝗦𝗢𝗡 Here's what actually changes day-to-day: Jenkins requires you to provision and maintain a build server, manage plugin compatibility (which breaks more than you'd expect), and context-switch between your repo and a separate UI. GitHub Actions gives you ephemeral runners — fresh environments spun up per job, then discarded. Your CI/CD config is a `.yml` file in the repo itself, versioned alongside the code it builds. Zero infrastructure to own unless you 𝘄𝗮𝗻𝘁 self-hosted runners for specific needs. The operational overhead difference is real. A small team on Jenkins often has one person who "knows how it works." That's a risk, not a feature. GitHub Actions isn't perfect — complex matrix builds and cost at scale are genuine pain points. But for most teams shipping software today, the default choice should be Actions, with Jenkins reserved for environments that 𝗿𝗲𝗾𝘂𝗶𝗿𝗲 deep customization or already have mature Jenkins infrastructure. 💬 𝗬𝗢𝗨𝗥 𝗧𝗨𝗥𝗡 Have you migrated from Jenkins to GitHub Actions — or gone the other direction? What was the deciding factor? 𝗪𝗮𝗻𝘁 𝘁𝗵𝗲 𝗱𝗮𝘁𝗮 𝗯𝗲𝗵𝗶𝗻𝗱 𝘁𝗵𝗶𝘀? JetBrains' 2026 report shows GitHub Actions leading CI/CD adoption at 33% in organizations, while EITT's deep-dive breaks down the full TCO — and maintenance cost alone makes Jenkins 60x more expensive for smaller teams. For SaaS teams specifically, Impressico found GitHub Actions cuts setup time by over 40% compared to Jenkins — dropping from days to hours. Links in the comments 👇 #DevOps #GitHubActions #Jenkins #SoftwareEngineering #Automation #CICD #TechCommunity #CloudComputing #Innovation #TechTrends TrainWithShubham