GitHub is sinking

# GitHub is sinking Source: [https://dbushell.com/2026/04/29/github-is-sinking/](https://dbushell.com/2026/04/29/github-is-sinking/) Wednesday 29Apr2026 **TL;DR:**GitHub used to be cool and now it’s a lame slop graveyard\. GitHub is racing towards the mythical[zero nines](https://en.wikipedia.org/wiki/High_availability#Percentage_calculation)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](https://mrshu.github.io/github-statuses/)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\. Line chart showing GitHub average uptime by month following the Microsoft acquisition\. A green line turns into an orange and red roller coaster\. [GitHub’s Historic Uptime](https://damrnelson.github.io/github-historical-uptime/)[Microsoft acquired GitHub](https://news.microsoft.com/announcement/microsoft-acquires-github/)and applied their unique brand of enshittification\. Amongst their achievements was the spawning of the[Copilot circle of hell](https://teybannerman.com/strategy/2026/03/31/how-many-microsoft-copilot-are-there.html)\. Now they’re effectively[DDoSing themselves with slop](https://github.blog/news-insights/company-news/an-update-on-github-availability/)\. 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\.](https://trunk.io/blog/what-happens-if-a-merge-queue-builds-on-the-wrong-commit)[Shameful\.](https://www.theregister.com/2026/03/26/github_ai_training_policy_changes/) As I write this the obituaries are flooding in: - [Ditching GitHub \- Lonami](https://lonami.dev/blog/ditching-github/) - [Ghostty Is Leaving GitHub \- Mitchell Hashimoto](https://mitchellh.com/writing/ghostty-leaving-github) - [Before GitHub \- Armin Ronacher](https://lucumr.pocoo.org/2026/4/28/before-github/) - [From GitHub to Codeberg/Forgejo \- Jonas Hietala](https://www.jonashietala.se/blog/2026/04/28/from_github_to_codebergforgejo/) **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](https://awesomeagents.ai/news/github-fake-stars-investigation/)is worthless\. GitHub is inundated with bots and[drowning in slop](https://www.theregister.com/2026/02/18/godot_maintainers_struggle_with_draining/)and doing everything to encourage it\. Microsoft is turning GitHub into the[Moltbook](https://en.wikipedia.org/wiki/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](https://codeberg.org/)— 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](https://forgejo.org/)\. [Tangled](https://tangled.org/)— an alpha stage start\-up with interesting[AT protocol](https://dbushell.com/2026/03/10/building-on-at-protocol/)integration\. Worth considering for smaller solo projects\. [Gitea](https://about.gitea.com/)— they offer cloud managed Git hosting\. It’s the original open source project that Codeberg/Forgejo forked away from\. [GitLab](https://about.gitlab.com/)— 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](https://bitbucket.org/)— 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](https://gothub.org/),[Radicle](https://radicle.dev/), and[Sourcehut](https://sr.ht/)were suggested to me\. I’ve no idea how they work, investigate yourself\! ## Self\-hosted If you’re[cool like me](https://dbushell.com/2025/08/11/github-ensloppification/), you or your organisation can self\-host a Git forge with[actions](https://dbushell.com/2025/08/15/self-hosted-forgejo-actions-runner/)and[releases](https://dbushell.com/2025/08/25/self-hosted-forgejo-actions-releases/)\. My recommendation is[Forgejo](https://forgejo.org/)\. There is[talk of federation](https://codeberg.org/forgejo-contrib/federation)between Forgejo instances \(**edit:**[and Tangled](https://blog.tangled.org/federation/)\) 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 [email protected]:/path/to/repo ``` 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\.