I was editing a wiki page, and the UI started telling me that someone else had edited the page and that I should refresh (refreshing resulted in the same message in short order). I'm the only maintainer!
It is definitely some form of confirmation bias, or I just use GitHub far too much, but I swear I encounter every GitHub outage within a few minutes of it happening. I'm working on some actions, there is an actions outage. I'm testing webhooks for some service and think I broke something, but nope, its a GitHub outage. Today I go to commit and my repo no longer exists...
I love GitHub, but these things seem to happen far too regularly.
for those saying you can't access your code, don't you all have a copy sitting on your computer in front of you? How do you use github as source control in a way that means when github goes down there's no code to work on?
What does your company do that you don't have Github or some equivalent centralization, such as Gitlab, self-hosted or not?
For the rest of us, Github (/etc.) is our primary means of transferring branches, a centralized "main" branch, and sometimes where CI/builds/test happen, as well as deployments. This isn't even bizarre … I've worked at 6+ companies now, and 100% of them followed this pattern. (Not all with Github, but they all had some centralized place to push/pull code and conduct reviews, tests, deployments…)
(I'd entertain the usual "is self-hosted worth it?" argument that tends to crop up in these threads. But this question is a bit off the wall.)
I can still commit to my local repository, of course, but at some point, I am going to need to share my work with coworkers or with production. During a normal day, that's several times per day, as features/branches are done & go out for review & merging…
Even the two places I've worked that self-hosted bare git repos on cheap Linux VMs (both times, due to management concern about Github snooping on private code), no fancy web UI or anything, it was used the same way GH is, with the server acting as the hub for collaboration.
git pull fails to work. The code you checked in last night and now are wanting to pull to your “copy sitting on your computer” can no longer happen, rendering your local copy stale. Do you work on stale code? Accessing code could also refer to them in their roles: maybe they are DevOps and their job is to wire up pipelines to deploy spaghetti to a giant furball k8s environment and they can’t because they can’t access their code.
Projects were at a real sweet-spot a couple years back. Milestones were great, between that and tags you could do everything you really needed to without a bunch of time-wasting fake-productive crap getting in the way like they do on "full featured" task trackers. Easy to navigate, easy to use, hard to lose stuff (am I the only one who's constantly losing stuff in other task tracking systems?)
Not that I was ever successful in getting anyone other than programmers to use it, though. Which I guess is why they made it worse, to try to court the kind of people who like Jira and Asana and Azure Devops (what a terrible name) and all that junk.
Yeah, completely blocked from pushing or pulling. Also, right before it looked like their slack integration notifs were delayed. Maybe their queue processing of that broke the site.
I had _just_ pushed an updated actions workflow, saw that it began to run, and noticed that my entire repository was 404-ing. Not gonna point fingers, but uh, sorry everybody.
Always ship on Friday afternoon. That way, you can rest easy all weekend knowing whatever task you thought you were going to have to do on Monday will be off your plate replaced by something you don't know about yet. Enjoy your weekend!
