GitHub is sinking
TL;DR · AI 摘要
GitHub的可靠性下降,用户体验变差,用户开始转向其他平台。
核心要点
- GitHub可靠性下降,用户体验变差
- 微软收购后GitHub变成昂贵的负债
- 用户开始转向其他Git托管平台
结构提纲
按章节快速跳转。
思维导图
用一张图看清主题之间的关系。
查看大纲文本(无障碍 / 无 JS 友好)
- GitHub可靠性下降
金句 / Highlights
值得收藏与分享的关键句。
GitHub的官方可靠性数据令人担忧,实际体验更差。
微软收购后,GitHub变成了昂贵的负债。
用户开始转向其他Git托管平台。
GitHub is sinking – David Bushell – Web Dev (UK)
dbushell.comfreelance
Menu
GitHub is sinking
SubscribeBlog RSS feedNotes RSS feedorCombined RSS feedand followMastodonBluesky
Wednesday 29 Apr 2026 Play Synthesised Audio
TL;DR: GitHub used to be cool and now it’s a lame slop graveyard.
GitHub is racing towards the mythical zero nines of uptime. Users are starting to notice that GitHub is now a Microsoft product. _Eww!_
Official uptime paints a concerning chart. The missing status page tell a far worse story. Whatever the truth, it’s impossible to miss the _delightful_ experience that is Microsoft GitHub if you use it semi-regularly.
Alt Line chart showing GitHub average uptime by month following the Microsoft acquisition. A green line turns into an orange and red roller coaster.
Microsoft acquired GitHub and applied their unique brand of enshittification. Amongst their achievements was the spawning of the Copilot circle of hell. Now they’re effectively DDoSing themselves with slop. I won’t dwell on what else went wrong. I don’t know and I don’t care. GitHub is impressively bad now. It’s embarrassing.Shameful.
As I write this the obituaries are flooding in:
- Ditching GitHub - Lonami
- Ghostty Is Leaving GitHub - Mitchell Hashimoto
- Before GitHub - Armin Ronacher
- From GitHub to Codeberg/Forgejo - Jonas Hietala
It’s long past time to get off this sinking ship!
Git is not GitHub
GitHub has become synonymous with “source control” and I worry too many users don’t know that Git is not GitHub. The core technology of Git is open source. It’s distributed, meaning that all repositories are equal. Git works without a centralised service. Such a practice is a construct of social convenience. GitHub was a useful add-on. Microsoft has turned GitHub into an expensive liability.
But network effect…
Network effects are hard to topple but if anyone can do it, Microsoft can. GitHub’s fake star economy is worthless. GitHub is inundated with bots and drowning in slop and doing everything to encourage it. Microsoft is turning GitHub into the Moltbook of code, it ain’t for you and me anymore.
But continuous integration…
Your CI pipeline is over-engineered and GitHub Actions are an abomination (see: [[1]](https://www.iankduncan.com/engineering/2026-02-05-github-actions-killing-your-team/)[[2]](https://nesbitt.io/2026/04/28/github-actions-is-the-weakest-link.html)). Finding another solution is an absolute chore but do you trust GitHub to be reliable?
But more excuses…
Look, the ship is sinking! Sure, the water looks freezing. Don’t hang around and allow Microsoft to pull you under. You don’t need to move everything in one go. Start the process.
Alternatives
The nearest lifeboat to escape GitHub is another centralised Git forge. Just sign up and push your repo to the new upstream. Some services can automate the migration and maybe even import issues. Personally I’d leave issues behind in a tragic boating accident.
Edit: none of the options below are 100% rainbows and butterflies. They are _not GitHub_, that’s all I can vouch for. Do your own research etc.
Codeberg — a non-profit and community-led project with an established track record. This is the safe alternative that’ll stick around. It’s the flagship instance of Forgejo.
Tangled — an alpha stage start-up with interesting AT protocol integration. Worth considering for smaller solo projects.
Gitea — they offer cloud managed Git hosting. It’s the original open source project that Codeberg/Forgejo forked away from.
GitLab — enterprise grade, meaning it’s bloated and confusing but it’ll impress your boss. This could be the choice if you need multiple meetings to make the choice.
Bitbucket — trade one soul destroying corpo fun vacuum for another. Strongly discouraged, but Bitbucket does technically fit the _anything but GitHub_ category.
Edit:Game of Trees, Radicle, and Sourcehut were suggested to me. I’ve no idea how they work, investigate yourself!
Self-hosted
If you’re cool like me, you or your organisation can self-host a Git forge with actions and releases. My recommendation is Forgejo. There is talk of federation between Forgejo instances (edit:and Tangled) but it’s not happening anytime soon. If you want open collaboration push a copy to Codeberg. Gitea and GitLab also have self-hosted options. Be aware, GitLab is a comparative chonker.
When I said “Git is not GitHub” the same applies to other forges. Do you need those add-ons? Nothing is stopping you from raw-doggin’ Git over SSH:
git clone user@192.168.1.67:/path/to/repoCopy Code How you manage collaboration is another question. If Linux can be maintained by sending patches to an email mailing list, _“doesn’t work at scale”_ arguments are skill issues. But seriously, a centralised Git forge is a decent compromise in my opinion. Maybe they collapse like GitHub in future. Always have an exit plan.
Just use anything but GitHub.
SubscribeBlog RSS feedNotes RSS feedorCombined RSS feedand followMastodonBluesky
Written by **human**
All opinions are my own and not those of a large language model. Everything I write is one hundred percent human. _Because I care!_
Web buttons



Copyright and privacy
Copyright© 2004–2026•Privacy policy•AI policy
Menu
Close menu