Why Ghostty is leaving GitHub: A wake-up call for developers

When a developer like Mitchell Hashimoto—someone who has lived and breathed GitHub for 18 years—decides to pack up and move, you should pay attention. Ghostty is leaving GitHub, and it isn't because of a whim or a sudden change in pricing. It’s because the platform has become a bottleneck for serious, high-velocity software engineering. If you’ve spent your morning staring at a spinning loading icon while trying to review a pull request, you already know exactly why this is happening.

The reality is that we’ve conflated Git with GitHub for too long. Git is a distributed version control system designed to be resilient and decentralized. GitHub, however, is a centralized service that has become a single point of failure for the modern software supply chain. When GitHub Actions goes down, or when the web interface hangs, your ability to ship code doesn't just slow down—it stops entirely.

Here is the hard truth about relying on a single platform for your entire development lifecycle:

1. Infrastructure fragility: You are at the mercy of their uptime. If their internal services fail, your CI/CD pipelines, issue tracking, and code review processes vanish.
2. Workflow lock-in: We’ve built our entire culture around PRs and GitHub-specific features. Moving away requires a massive shift in how teams collaborate.
3. The "Distributed" Myth: While your local repo is safe, your project's metadata—the history of decisions, the community discussions, and the automated testing—is trapped in a proprietary silo.

Most people get tripped up by thinking that because Git is distributed, their project is safe. That’s a dangerous misconception. Your code might be safe on your laptop, but your project’s velocity is entirely dependent on the platform’s health. When you can't merge a PR because the platform is struggling, you aren't working in a distributed environment; you're working in a centralized one with a fancy interface.

This next part matters more than it looks: the decision to move Ghostty isn't just about one project. It’s a signal that the "GitHub-first" era of open source is facing a crisis of reliability. If the platform can't support the basic needs of maintainers who are trying to ship software, then the platform is no longer a tool—it’s a liability.

Are you prepared to migrate your own infrastructure if your primary host fails you tomorrow? Most teams don't have a plan for this, which is exactly why they stay put even when the service degrades. You need to evaluate your dependency on centralized platforms before you find yourself locked out of your own repository during a critical release window.

The move away from GitHub is a bold step toward reclaiming control over the development process. It’s a reminder that we should prioritize tools that offer stability over those that offer convenience. If you’re tired of fighting against your own infrastructure, it might be time to start looking at alternatives that treat your time as a valuable resource rather than a metric to be throttled.

If you’re feeling the same frustration with GitHub reliability, start auditing your own project dependencies today and share what you find in the comments. Read our breakdown of decentralized development workflows next to see how you can insulate your team from future platform outages.