Mitchell Hashimoto is migrating Ghostty off GitHub after months of near-daily outages blocking Actions, PR review, and Issues – not Git itself.
Key Takeaways
Hashimoto kept a daily journal marking outage impact with X; almost every day had one, including a ~2-hour Actions outage the day he published.
The issue is infrastructure around Git – Actions, Issues, PRs – not the distributed version control layer.
Migration is incremental; a read-only mirror stays at the current GitHub URL while discussions continue with both commercial and FOSS providers.
Personal projects and other open source work remain on GitHub for now; Ghostty maintainers and community are the primary affected group.
Final decision was made this week but the plan has been in motion for months, predating the April 27 ElasticSearch outage.
Hacker News Comment Review
Commenters are split on root cause: Microsoft acquisition shifting engineering resources to Copilot, AI-generated code degrading codebase quality, or organizational culture drift – with no consensus on which dominates.
The sentiment that GitHub reliability decay is part of a broader web-quality regression (constant outages, UI papercuts, incomplete features) got significant agreement, framing this as industry-wide rather than GitHub-specific.
Alternative forges surfaced in comments: tangled.org drew attention for decentralizing centralized GitHub features using atproto-based identity, addressing the multi-account fragmentation problem that makes forge switching costly.
Notable Comments
@tedivm: points to an unofficial GitHub status page as evidence of a “horrifying” reliability trajectory, independent of Hashimoto’s personal account.
@varun_ch: flags tangled.org as a decentralized forge using atproto identity – potentially reducing the account-per-forge friction that keeps developers locked into GitHub despite quality issues.
