Fetching from the wire…
Top 5 · 2026-04-29 · source-backed
Mitchell Hashimoto, founder of HashiCorp, announced that Ghostty is leaving GitHub after 18+ years of hosting projects on the platform. His reason: near-daily outages and GitHub Actions disruptions making serious development impossible. The post hit 2,614 points and 766 comments on Hacker News, making it the day's top story by a wide margin.
Hashimoto is evaluating Codeberg, GitLab, and self-hosted Gitea/Forgejo as alternatives. A read-only GitHub mirror will remain. The HN comments split predictably: some arguing GitHub's reliability is fine for most projects, others sharing their own outage war stories, and a healthy contingent pointing out that GitHub Actions has become a single point of failure for the entire open source ecosystem.
I find this story significant beyond one project's migration. Hashimoto isn't a random developer venting. He built the company behind Terraform, Vagrant, Consul, and Vault. When someone with that track record says the platform is unreliable, it carries weight.
The timing makes it more interesting. In the same week, GitHub is restructuring its entire billing model (story #1), adding consumption-based pricing for Copilot, and charging Actions minutes for code review. GitHub is simultaneously getting less reliable AND more expensive. That's not a great combination for retaining developers who have alternatives.
I don't think there's going to be a mass exodus from GitHub. The network effects are too strong, the ecosystem too deep. But I think we're entering a period where smart teams diversify their git hosting. Keep the GitHub mirror for visibility and contributor access. Run your CI and primary development on something you control. The CVE-2026-3854 disclosure from Wiz Research this month, a CVSS 8.7 command injection in GitHub's internal git protocol that could've exposed millions of repos, reinforces the point. Platform risk is real.
For builders: if your CI, code hosting, project management, and AI coding assistant all run through GitHub, you've got concentration risk. At minimum, make sure your Actions workflows can run elsewhere.
Each link below shares sources, entities, or timing with this story.
Mitchell Hashimoto works at HashiCorp / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Mitchell Hashimoto works at HashiCorp); both cover Copilot, GitHub, GitHub Actions, HashiCorp; overlapping topics (action, hashimoto, platform).
Linked by a graph relationship (Mitchell Hashimoto works at HashiCorp); both cover Ghostty, Mitchell Hashimoto, Terraform, Vagrant; overlapping topics (action, ghostty).
Claude Code uses Terraform / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Terraform); both cover Copilot, CVE, CVSS, GitHub; overlapping topics (action, code).
Copilot uses Claude / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Copilot uses Claude); both cover Actions, Copilot, GitHub, When; overlapping topics (action, code).
Claude Code uses Terraform / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses Terraform); both cover GitHub, GitLab, Hacker News; reported by the same outlet (news.ycombinator.com).
Claude Code uses Terraform / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code uses Terraform); both cover Hacker News, When; reported by the same outlet (news.ycombinator.com).
Claude Code uses Terraform / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses Terraform); both cover Actions, GitHub, GitHub Actions; overlapping topics (action, code, platform).
Mitchell Hashimoto works at HashiCorp / Shared entities / Earlier coverage
Linked by a graph relationship (Mitchell Hashimoto works at HashiCorp); both cover GitHub, GitHub Actions, HashiCorp, Mitchell Hashimoto; earlier GitHub coverage from 2026-02-22.