Ghostty Is Leaving GitHub
TLDR
- Mitchell Hashimoto is migrating Ghostty off GitHub after near-daily outages made it unusable for serious open source work.
Key Takeaways
- Hashimoto tracked GitHub outages in a journal for a month; almost every day had an X marking lost work time.
- On the day he published this post, a GitHub Actions outage blocked PR review for roughly two hours.
- The April 27, 2026 ElasticSearch outage is separate; the decision to leave had been in progress for months.
- Ghostty will keep a read-only mirror at the current GitHub URL; Hashimoto’s personal projects stay on GitHub for now.
- A migration plan is underway with multiple providers under evaluation, both commercial and FOSS, with incremental dependency removal.
Why It Matters
- A high-profile open source maintainer publicly citing reliability as the reason to leave signals a credibility problem for GitHub as infrastructure.
- The critique targets GitHub’s surrounding infrastructure (issues, PRs, Actions), not Git itself, narrowing the scope of what any replacement must solve.
- The move sets a visible precedent for other maintainers weighing reliability costs against GitHub’s network effects.
Mitchell Hashimoto · 2026-04-28 · Read the original