Comments like this are so frustrating to see, as my company goes backwards, moving from Gitlab to GitHub.
Comment on GitHub Has an Availability Problem. Is It Time to Look Elsewhere?
danielquinn@lemmy.ca 4 days ago
The right time to look elsewhere was when Microsoft bought it.
The next best time was when viable alternatives like GitLab and later, Codeberg appeared.
The next best time was when it became clear that they were stealing your code to feed into their sparkly autocomplete and were going to sell it back to you.
The next best time was when they dumped a bunch of vibecoded garbage into the codebase and killed the uptime.
The next best time is now.
You don’t even have to migrate all your stuff. Just start all your new projects on Codeberg, or GitLab, or something self-hosted. Once you get used to the new place, you can migrate your old stuff when you’re ready.
AA5B@lemmy.world 3 days ago
boonhet@sopuli.xyz 3 days ago
I mean, didn’t Gitlab also say they were going all-in on AI?
There’s no major forge you can use for proprietary projects that isn’t shitty.
AA5B@lemmy.world 2 days ago
Don’t remind me …. The doublespeak at my company …… we had to use GitHub for the built in AI, but couldn’t even evaluate GitLab’s AI because it costs extra
axolotl_cpp@feddit.it@feddit.it 2 days ago Forgejo, if you self host it, you can use it for propietary projects
(And it’s as easy as deploying a docker container and hitting start, really)boonhet@sopuli.xyz 2 days ago
Yes, but then you hold all the liability for your shit going missing. The entire point of using a managed service like github or gitlab is that you have someone to sue.
- axolotl_cpp@feddit.it@feddit.it 2 days ago
Codeberg/Forgejo also have a simple button to migrate directly on the web UI
dan1101@lemmy.world 4 days ago
This is exactly it, Microsoft always makes things about themselves. They change everything, mostly for the worse.