Vibe-served.
“Tactical downtime”
it went down literally half an our after our company announced we would also bring our CI Pipeline over to GitHub…
That makes my day, most of the time the universe doesn’t go that hard that fast.
There are downsides to being unemployed for sure, but not knowing that Github is down until I see it on social media is quite an upside 😌
I’ll pour out a bit of coffee for all those who still have to care about these things o7
I did not notice until I saw it on a site. Ah, if only the savings would last forever, so that I do not have to return to the workforce.
Its always DNS.
It used to be DNS. Now slop commits and shoddy QA are more likely.
Not always. Sometimes it’s the firewall.
Or those fucking gnomes
I decided against using Github for my personal stuff since it’s owned by Microsoft.
I can’t help but feel a little bit smug every time it shits the bed nowadays.
That feeling might schadenfreude, and it’s heavenly.
This is why I don’t use GitHub. Well that and I don’t code.
Have you considered using it for hosting a small personal blog instead?
(There might be better options, but this is the first one I became aware of)
I don’t code either but prefer the Gitea instance in my basement over anything MS hosts.
Lol, I recently interviewed with a company who thought it was a good idea to put their entire codebase and CI into github. They didnt see a problem with it…
I mean, internal CI and version control systems go down too. Like, if GitHub has substantially worse downtime than an whatever internal system one runs, fair enough.
Git’s distributed, so downtime isn’t usually a huge deal compared to a non-distributed version control system.
I think that the largest issue is actually that GitHub provides a centralized commit review system (and, to be fair, so are many internal systems) that one uses to review pull requests. Like, a CI run being deferred usually isn’t a huge deal. Version control is probably distributed these days. But code review is something that you’d like to keep going.
If you do code review in email or something, it’s distributed. You can keep working. If your email server goes down, it might prevent new messages from reaching other users, but all of the review requests you have can be worked on and any review you’ve already received can be read. But if people are using some centralized Web-based code review system, and that goes down, then that kinda halts a lot of stuff.
Same centralized problem for issue tracking.
EDIT: I’ve never used a distributed issue tracker, but apparently they are indeed out there:
https://github.com/git-bug/git-bug
EDIT2: A lot of issue trackers involve people attaching large files to issues, so there might be some fundamental scalability issues in that regard for distributed operation; might need to centralize that part. That being said, I’d rather temporarily lose access to just a large-file-hosting server than to that and all of the other issue data.
Ironically, on Github
It looks like it supports bridging to GitHub and a number of other issue trackers, so while the project is using GitHub’s issue tracker, I’d bet that the devs are using their own system to interface with it.
My company luckily didn’t do this…
/BearLookawayMeme
Ours has been there for over a decade, It’s not ideal, but moving it all is an undertaking. Over the years we’ve created alternative methods to work around the CI when it’s down, Ideally we’d host our own
The “cloud” 👍
Github seems to bug out quite a lot. More than once I had to reload the page a handful of times until my browser deemed it safe.
I migrated every single repo to GitHub (from GitLab) yesterday. Today was a short day.
Why would you go to microslop?
Because all my pleading to host our own forgejo was ignored. It’s not as if I had much choice in my job if my company’s IT decides to switch.
Ah, so it was IT management deciding, the ever corrupt, ever incompetent fuckers in every organisation. Okay, I feel that pain.
It’s nice working somewhere with GitHub enterprise at times
Good!