The easy version of this story is that Mitchell Hashimoto got fed up with GitHub outages and decided to move Ghostty elsewhere.

The more interesting version is that one of the most recognizable maintainers in modern developer tooling just said the center of gravity for open source no longer feels dependable enough for serious work. That is not a complaint about one bad afternoon. It is a complaint about monoculture.

Hashimoto's post lands because it is personal, but the argument is structural. Git was supposed to make source control distributed. In practice, most projects rebuilt a centralized control plane on top of it: issues, pull requests, CI, release automation, discussions, identity, and reputation. When that layer gets flaky, "just use Git" is not an answer. It is a dodge.

What is actually verified

The primary source is Hashimoto's own post: "Ghostty Is Leaving GitHub," published on April 28.

He says Ghostty will leave GitHub, keep a read-only mirror at the current URL, and move incrementally because the project depends on more than raw Git hosting. He also says the team has been planning this for months and that the timing is only coincidentally close to GitHub's large April 27 outage. The final provider has not been announced yet. He writes that he is still in discussions with multiple commercial and open-source options.

The post is blunt about why. Hashimoto says he has been marking down each day that a GitHub outage disrupted his work, and that almost every day in the past month earned an X. He describes repeated GitHub failures as something that now blocks code review, shipping, and day-to-day maintenance work. That journal is his own record, not an independently audited uptime dataset, but the broader claim that GitHub has had a rough stretch is not hard to corroborate.

A separate Reddit-hot thread linked GitHub's own availability update from the same week, and Hacker News pushed Hashimoto's post to the front page with thousands of points and hundreds of comments. The public reaction was not mostly "wow, dramatic blog post." It was a lot of developers saying some version of: yes, the service quality problem is real, and yes, too much of modern software delivery now sits behind one vendor's control plane.

Why this matters beyond Ghostty

Ghostty is not leaving because Git itself failed. It is leaving because the layer around Git has become the real product.

That point matters more than the migration itself. Plenty of people still talk as if leaving GitHub is just a question of moving a repository and updating a remote URL. That was never the whole job, and it is even less true now. Maintainers depend on issue history, pull request review, Actions, bot integrations, access control, release pipelines, and a contributor graph that lives inside GitHub's walls. Open source stayed portable at the protocol level while getting sticky everywhere else.

That stickiness looked efficient when GitHub was stable. It looks riskier when maintainers start describing outages as a routine part of the workday.

There is also a timing problem here that goes beyond uptime charts. GitHub is trying hard to sell itself as the default home for AI-assisted and agent-heavy software development. That means more generated commits, more CI runs, more automated review loops, and more workflow pressure on the same centralized surface area. Several Reddit and Hacker News comments picked up exactly that contradiction: a platform pushing agentic coding at scale should be better than average at staying up for the boring parts.

If the boring parts wobble, the AI pitch starts to sound backward. Fancy assistance does not help much when review queues stall, Actions break, or maintainers cannot trust the basic operational floor under the project.

The stronger takeaway is about concentration risk

A lot of developer infrastructure discourse still acts as if concentration risk is something that happens to clouds, package registries, or identity providers, but not to source control. That feels outdated.

GitHub is not just where code is stored. For many projects it is where governance happens, where contributions are judged, where automation runs, and where software gets packaged into a legible public record. That makes it infrastructure in the same way DNS or CI secrets managers are infrastructure. People can tell themselves there are alternatives, and there are, but switching costs only stay theoretical until somebody actually tries to move a living project with a real community.

That is why Hashimoto's post hit so hard. He is not an outsider taking a cheap shot. He is someone who spent nearly two decades treating GitHub as the natural home for open source work and still decided the cost of staying had become higher than the cost of leaving. That is a different kind of signal.

What remains uncertain

A few points need careful labeling.

First, the move destination is still unknown. Hashimoto says discussions are ongoing, so any claim that Ghostty is definitely heading to a specific forge would be guesswork.

Second, his daily outage journal is a first-person account, not a public dataset. It is evidence of one high-activity maintainer's experience, not a formal service-level analysis.

Third, the deeper cause of GitHub's recent reliability complaints is still interpretation territory. Public commenters blamed everything from Microsoft's ownership to internal priorities around Copilot to plain scale strain. Those are theories. What is verified is simpler: experienced maintainers and developers are reporting disruption, and at least one major project is now exiting the platform.

What developers should do with this

If you maintain software on GitHub, the obvious lesson is not "panic and migrate tomorrow." It is to take your dependency stack around GitHub more seriously.

Know which parts of your workflow are portable and which are not. Know how much project memory only exists in issues and PRs. Know what breaks if Actions goes down for half a day. Know whether you can mirror, export, or rebuild the social and automation layer around your repository if you have to.

The open-source world spent years saying GitHub was convenient because Git is distributed underneath it. That was true, but incomplete. The real lock-in was never the commit history. It was the workflow gravity around the commits.

Ghostty leaving GitHub does not prove the GitHub era is over. It does show that maintainers are getting less willing to treat convenience as a substitute for resilience. That is probably overdue.

Sources