I spent hours trying to figure out what was wrong with GHCR, &^$% Github.
I'm on the lookout for an alternative, this really is not acceptable.
GitHub having issues [resolved]
101–110 of 150 posts
Re: GitHub having issues [resolved]
#102has anyone at MS tried unplugging azure and plugging azure back in yet?
It's Microsoft. You're supposed to Ctrl+Alt+Del.
Re: GitHub having issues [resolved]
#103I really wish Graphite had just gone down the path of better Git hosting and reviewing, instead of trying to charge me $40 a month for an AI reviewer. It would be nice to have a real first class alternative to Github
Codeberg?
Re: GitHub having issues [resolved]
#104Earlier quoted context omitted.
Except actually it was, that was what my git client was reporting trying to run a pull.
I'm going to trust the constant stream of updates from the company itself which shows exactly what went down and came back up rather than a random anecdote.
If you look at the incident details it also claims most services were impacted.
> Git Operations is experiencing degraded availability. We are continuing to investigate.
Re: GitHub having issues [resolved]
#105Re: GitHub having issues [resolved]
#106Maybe we should turn these weekly posts into an actionable item we can use to move organizations away from this critical infrastructure that is failing in realtime.
Re: GitHub having issues [resolved]
#107I would so very much love to see GitHub switch gears from building stuff like Copilot etc and focus on availability
The #1 priority at GitHub for this year is migrating from their own data center to Azure, any other work that gets in the way of this is being deprioritized: https://thenewstack.io/github-will-prioritize-migrating-to-a...
> It’s existential for GitHub to have the ability to scale to meet the demands of AI and Copilot, and Azure is our path forward. W
More existential than going down a few times a week?
Re: GitHub having issues [resolved]
#108Earlier quoted context omitted.
Except actually it was, that was what my git client was reporting trying to run a pull.
I'm going to trust the constant stream of updates from the company itself which shows exactly what went down and came back up rather than a random anecdote.
Recent years have shown this to be the wrong prediction strategy. The reason seems to be an incentive imbalance where there are quite a few reasons for companies to lie (including their own CLAs) and not a lot of repercussions for doing so (everybody competes on lock-in, not on product). Of course, the word-of-mouth approach is also exploitable by dishonest actors, but thus far there doesn’t look to be a lot of exploitation going on, likely because there’s little reason to bother (once again, lock-in is king).
Re: GitHub having issues [resolved]
#109> This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. does anyone know where these "detailed root cause analysis" reports are shared? is there maybe an archive?
They get posted to the incident log (https://www.githubstatus.com/incidents/n07yy1bk6kc4) for example https://www.githubstatus.com/incidents/lcw3tg2f6zsd.
There are also monthly availability reports: https://github.blog/tag/github-availability-report/
Re: GitHub having issues [resolved]
#110Insert the standard comment about how git doesn't even need a hub. The whole point of it is that it's distributed and doesn't need to be "hosted" anywhere. You can push or pull from any repo on anyone's machine. Shouldn't everyone just treat GitHub as an online backup? Zero reason it being down should block development.