Mitchell Hashimoto is migrating Ghostty off GitHub after near-daily GitHub Actions, PR, and infrastructure outages made serious development work impossible.
Key Takeaways
Hashimoto kept a journal marking GitHub outage days; almost every day had an X, including a ~2-hour Actions outage the day he published this post.
The move is planned and incremental, not reactive: discussions started months ago, a destination provider is still being finalized (commercial and FOSS options both in play).
A read-only mirror will stay at the current GitHub URL; personal projects remain on GitHub for now; only Ghostty moves first.
The footnotes are explicit: the problem is not Git itself but the surrounding infrastructure: issues, PRs, Actions.
Hacker News Comment Review
Commenters broadly agree GitHub quality has visibly degraded, pointing to Microsoft acquisition priorities, resource concentration on Copilot, and alleged reliance on vibe coding as compounding causes; an unofficial status page is cited as evidence.
Technical commenters surfaced git-bug as a way to store issues and PRs inside the Git repo itself, and Codeberg as a likely forge destination, framing distributed-issue tooling as the real migration challenge.
A recurring thread argues the emotional pain was structurally predictable: GitHub was always a non-free, third-party-controlled platform, and the Microsoft acquisition reversed the service relationship from user-first to investor-first.
Notable Comments
@tedivm: Points to an unofficial GitHub status page as concrete evidence of ongoing reliability collapse beyond anecdote.
@nextaccountic: Recommends git-bug for storing issues and PRs natively in git refs, with two-way sync to multiple forges, as a portable alternative to GitHub’s issue tracker.
