GitHub has become unreliable and slop-ridden post-Microsoft acquisition; the author urges migrating to Codeberg, Forgejo, GitLab, or self-hosted Git over SSH.
Key Takeaways
Uptime data shows GitHub reliability degrading significantly after the Microsoft acquisition, with the official status page understating actual outages.
GitHub Copilot and AI-generated code have flooded the platform with bot activity and low-quality repos, accelerating decline.
Git is decentralized by design; GitHub is just a social layer on top, and that layer is now a liability.
Recommended exits: Codeberg (non-profit, Forgejo-based), Forgejo self-hosted, GitLab (enterprise-grade but bloated), Gitea, or raw Git over SSH.
GitHub Actions are called out as over-engineered; migrating CI is painful but GitHub’s reliability makes staying a risk.
Hacker News Comment Review
Commenters split on root cause: some attribute degradation to AI-driven commit volume overwhelming GitHub’s infra; others note the uptime chart shows problems starting in 2020, well before LLM coding took off.
Real user friction is confirmed: rate limits on basic browsing like commit history are hitting solo users on dedicated IPs, not just CI bots.
The uptime graph’s pre-acquisition 100% figure drew skepticism, suggesting the baseline may reflect incomplete status page reporting rather than actual perfection.
Notable Comments
@oarsinsync: Hit a secondary rate limit just clicking “commits” on a repo, on a dedicated IP with no other GitHub traffic.
