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 Comments
cupcakezealot@piefed.blahaj.zone · 66 pts · 298d
codeberg is up tho
carrylex@lemmy.world · 34 pts · 298d
Codeberg win
hopesdead@startrek.website · 53 pts · 298d
The original said the code is compiling.
jol@discuss.tchncs.de · 24 pts · 298d
Now the AI is "thinking"
bitwolf@sh.itjust.works · 2 pts · 298d
And then Microsoft bought github and managed to waste even more time than bad compiles
bleistift2@sopuli.xyz · 19 pts · 298d
Has Github been down this often before Microsoft took over?
mesamunefire@piefed.social · 29 pts · 298d
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!
nogooduser@lemmy.world · 3 pts · 298d
I find this very odd because Azure DevOps is hardly ever down in our experience.
mesamunefire@piefed.social · 1 pts · 298d
I don't think they are on azure yeah?
tdawg@lemmy.world · 2 pts · 298d
They mostly aren't. They just announced they will be migrating the entire system to azure in the coming months tho
tdawg@lemmy.world · 1 pts · 298d
Damn man. It took me months to convince the team to get off azdo
marcos@lemmy.world · 8 pts · 298d
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.
Ephera@lemmy.ml · 7 pts · 298d
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.
carrylex@lemmy.world · 3 pts · 298d
That was so long ago I don't think that's comparable. But you can read through the availability report history
IcyToes@sh.itjust.works · 15 pts · 298d
Who knew a distributed VCS needed a connection to write and commit code...
supersquirrel@sopuli.xyz · 12 pts · 298d
Remember when tech workers were treated this well by their employers?
boonhet@sopuli.xyz · 10 pts · 298d
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.
tdawg@lemmy.world · 4 pts · 298d
Small teams ftw
boonhet@sopuli.xyz · 1 pts · 298d
Absolutely!
Unless you have assholes on your team. Luckily I haven't had many.
explodicle@sh.itjust.works · 3 pts · 297d
Why not just keep working with your local copy, and commit when the server is back up?
mesamunefire@piefed.social · 3 pts · 298d
Yep at work gonna get a coffee.
onlinepersona@programming.dev · 2 pts · 298d
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.