GitHub 'No Longer a Place For Serious Work', Says Hashicorp Co-Founder

Why It Matters

Frequent reliability failures at GitHub threaten developer productivity and could push high‑profile open‑source projects toward competing code‑hosting services, reshaping the ecosystem.

Key Takeaways

• HashiCorp co‑founder Mitchell Hashimoto cites daily GitHub outages
• Ghostty terminal project will migrate off GitHub after 18 years
• Outages include recent GitHub Actions and Elasticsearch failures
• Hashimoto demands tangible reliability improvements before returning
• Migration plan involves read‑only mirror and exploring commercial/FOSS alternatives

Pulse Analysis

GitHub’s reputation as the default hub for open‑source collaboration has been eroding under a wave of reliability incidents. Over the past month, the platform suffered multiple outages affecting GitHub Actions, pull‑request processing, and an Elasticsearch indexing glitch that left developers unable to review code for hours. Such disruptions are not merely inconveniences; they translate into delayed releases, increased operational costs, and a loss of trust among power users who rely on continuous integration pipelines to ship software at speed.

Mitchell Hashimoto, co‑founder of HashiCorp and maintainer of the Ghostty terminal emulator, publicly chronicled his frustration by marking nearly every day with an "X" in a personal outage journal. After 18 years of hosting Ghostty on GitHub, he decided to relocate the project, citing the platform’s inability to support “serious work.” His migration plan includes a read‑only mirror on GitHub while he evaluates both commercial and community‑driven alternatives. This move underscores a growing willingness among high‑profile developers to diversify their code‑hosting strategy rather than remain locked into a single, unreliable service.

The broader market implications are significant. As flagship projects contemplate leaving GitHub, competitors such as GitLab, Bitbucket, and emerging self‑hosted solutions gain traction. For Microsoft‑owned GitHub, the challenge is clear: convert promises of reliability into measurable uptime and performance guarantees. Failure to do so could accelerate a shift toward a more fragmented hosting landscape, prompting enterprises and open‑source communities alike to prioritize resilience as a core selection criterion.