Kinda. Less people used it back then so less eyes on downtime.
But its been a couple of times per month for a while now. And its causing delays at work. Here's to hoping they mess up enough that we can switch to something better!
Yeah, it didn't have CI runners or complex project management features. Pushing code can be done later. Looking at open-source issues can be done later.
22 replies
codeberg is up tho
Codeberg win
The original said the code is compiling.
Now the AI is "thinking"
And then Microsoft bought github and managed to waste even more time than bad compiles
Has Github been down this often before Microsoft took over?
Kinda. Less people used it back then so less eyes on downtime.
But its been a couple of times per month for a while now. And its causing delays at work. Here's to hoping they mess up enough that we can switch to something better!
I find this very odd because Azure DevOps is hardly ever down in our experience.
I don't think they are on azure yeah?
They mostly aren't. They just announced they will be migrating the entire system to azure in the coming months tho
Damn man. It took me months to convince the team to get off azdo
I think it used to be down more often. But it's been a long time and memories aren't reliable.
What changed is that it mostly only did git, that isn't in a time-sensitive work process. So nobody cared much if it was down.
Yeah, it didn't have CI runners or complex project management features. Pushing code can be done later. Looking at open-source issues can be done later.
That was so long ago I don't think that's comparable. But you can read through the availability report history
Who knew a distributed VCS needed a connection to write and commit code...
Remember when tech workers were treated this well by their employers?
We still are if you find a smaller company run by people who love tech, not just money. It's not as easy to find as big tech jobs used to be though.
Small teams ftw
Absolutely!
Unless you have assholes on your team. Luckily I haven't had many.
Why not just keep working with your local copy, and commit when the server is back up?
Yep at work gonna get a coffee.
Once radicle becomes viable and federated source forges are finally in vogue, github can suck it and these kinds of things will belong to the past.