Quit Yapping
The painful death of Github
35:12
Watch on YouTube ↗
T
Theo - t3.gg·Tech

The painful death of Github

TL;DR

GitHub has become dangerously unreliable — with reverted merges, 86% uptime, no CEO, and an npm malware incident — forcing developers to abandon it.

Key Points

  • 1.GitHub's real uptime has collapsed to 86.75%. A community-built alternative status page tracking any downtime across any service shows GitHub is nearly at 85% uptime — far worse than the official 99.5%-floor chart suggests.
  • 2.GitHub reverted ~2,844 merged pull requests in a single incident. A merge queue bug caused squash/rebase commits to generate from the wrong base state, potentially leaving production code out of sync with what exists in GitHub's history.
  • 3.COO Kyle's public response was widely condemned as dismissive. He framed the mass-revert as a 'regression in merge queue behavior' with changes 'appearing reverted,' offering no apology and extending the time window to shrink the percentage of affected PRs.
  • 4.GitHub has no CEO and a broken org structure. After Thomas Dohmke left, Microsoft assigned GitHub to an EVP with no coding background who also oversees Azure and Copilot; product and engineering teams operate in separate silos with no shared leadership to synchronize them.
  • 5.A remote code execution vulnerability was discovered the same day. A researcher found that unsanitized strings passed via git push could break out of internal headers and execute arbitrary code, granting access to millions of repositories.
  • 6.Mitchell Hashimoto (GitHub user #1,299, creator of Vagrant/Terraform/Ghosty) announced he is leaving after 18 years. He kept a daily journal for a month marking every day GitHub blocked his work — nearly every day had an X.
  • 7.GitHub/npm's negligence enabled real malware under the Tanstack name. Tanner Linsley, creator of Tanstack, had been reporting a malicious name-squatter for months or years; the squatted package was eventually compromised with a post-install script that exfiltrates .env files, confirmed by Socket.
  • 8.The creator frames GitHub's failure across four escalating trust tiers. These are: (1) does it work as before, (2) is it up right now, (3) does yesterday's work persist, and (4) can others steal your work — GitHub is now failing all four simultaneously.

Life's too short for long videos.

Summarize any YouTube video in seconds.

Quit Yapping — Try it Free →