Mitchell Hashimoto (GitHub user #1299, 18-year daily user) is migrating Ghostty off GitHub after near-daily outages blocked PR review for hours at a time.
Key Takeaways
Hashimoto kept a daily journal for a month; almost every day had an outage that blocked his work, including a 2-hour GitHub Actions failure.
An April 28 incident independently caused pull requests to fail due to an Elasticsearch failure, reinforcing the pattern after he wrote his post.
Ghostty will move incrementally to a new host (commercial or FOSS, still being evaluated); a read-only GitHub mirror stays, personal projects remain.
Microsoft’s AI push and the GitHub reliability decline are concurrent; the article notes the timing but stops short of asserting causation.
Hashimoto leaves the door open for return if GitHub delivers “real results and improvements, not words and promises.”
Hacker News Comment Review
Commenters largely validated the reliability complaints, with one reporting active pain from migrating CircleCI workloads onto GitHub Actions during the same instability window.
GitLab is not seen as a clean escape: the dominant counterpoint is that GitLab ignores serious bugs while burning resources on cosmetic UI changes.
There is real concern about a slow exodus of high-profile OSS projects, but no consensus on a credible alternative platform to land on.
Notable Comments
@WestCoader: migrating everything from CircleCI to GitHub Actions right now and finding Azure Repos/Pipelines was actually more stable than current GitHub.
@sikozu: wonders who leaves next; doesn’t expect mass Forgejo migration but thinks GitHub should be worried about the signal.
