141–150 of 425 posts
Earlier quoted context omitted.
They didn't migrate yet.
Fucking REALLY?!
Pages and Packages completed in 2025.
Core platform and databases began in October 2025 and are in progress, with traffic split between the legacy Github data center and Azure.
Screw GitHub, seriously. This unreliability is not acceptable. If I’m in a position where I can influence what code forge we use in future I will do everything in my power to steer away from GitHub.
Forge feature parity is easy to find. But GH has that discover ability feature and the social queues from stars/forks. One solution I see is (eg) internal forge (Gitlab/gitea/etc) and then mirrored to GH for those secondary features. Which is funny. If GH was better we'd just buy their better plan. But as it stands we buy from elsewhere and just use GH free plans.
Mirroring is probably the way forward.
Earlier quoted context omitted.
Github lost at least one 9, if not two, since last year's "existential" migration to Azure.
Is there any reason why Github needs 99.99% uptime? You can continue working with your local repo.
I’m guessing they’re regretting it.
Earlier quoted context omitted.
Github lost at least one 9, if not two, since last year's "existential" migration to Azure.
Is there any reason why Github needs 99.99% uptime? You can continue working with your local repo.
If you'd have asked me a few years ago if anything could be an existential threat to github's dominance in the tech community I'd have quickly said no. If they don't get their ops house in order, this will go down as an all-time own goal in our industry.
This should not be normal for any service, even at GitHub's size. There's a joke that your workday usually stops around 4pm, because that's when GitHub Actions goes down every day.
I wish someone inside the house cared to comment why the services barely stay up and what kinds of actions are they planning to do to fix this issue that's been going on years, but has definitely accelerated in the past year or so.