Monolith looking like a good now?
GitHub is down again
291–300 of 425 posts
Re: GitHub is down again
#292Earlier 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 a firm believer that almost nothing except public services needs that kind of uptime...
We've introduced ridiculous amounts of complexity to our infra to achieve this and we've contributed to the increasing costs of both services and development itself (the barrier of entry for current juniors is insane compared to what I've had to deal with in my early 20s).
Re: GitHub is down again
#293Meanwhile, Codeberg and Worktree are both online and humming along. Codeberg gets hit by a fair few attacks every year, but they're doing pretty well, given their resources. I am _really_ enjoying Worktree so far.
For anyone else having trouble finding Worktree's site because you keep getting "how to use git-worktree" results, it's https://worktree.ca/
Re: GitHub is down again
#294Meanwhile, Codeberg and Worktree are both online and humming along. Codeberg gets hit by a fair few attacks every year, but they're doing pretty well, given their resources. I am _really_ enjoying Worktree so far.
For anyone else having trouble finding Worktree's site because you keep getting "how to use git-worktree" results, it's https://worktree.ca/
Sorry! I should have included a link, since it's relatively unknown.
Re: GitHub is down again
#295Screw 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.
Every company I’ve worked in the last 10 years used GH for the internal codebase hosting , PRs and sometimes CI. Discoverability doesn’t really come into picture for those users and you can still fork things from GitHub even if you don’t host your core code infra on it
Re: GitHub is down again
#296I wonder if the incident root cause analysis will point to vibe coding?
Re: GitHub is down again
#297What are good alternatives to GitHub for private repos + actions? I'm considering moving my company off of it because of reliablity issues.
I've been using https://radicle.xyz/ + https://radicle-ci.liw.fi/ (in combination with my own ci adapter for nix flakes) for about half a year now for (almost) all my public and private repos and so far I really like it.
Re: GitHub is down again
#298We've migrated to Forgejo over the last couple of weeks. We position ourselves[0] as an alternative to the big cloud providers, so it seemed very silly that a critical piece of our own infrastructure could be taken out by a GitHub or Azure outage.
It has been a pretty smooth process. Although we have done a couple of pieces of custom development:
1) We've created a Firecracker-based runner, which will run CI jobs in Firecracker VMs. This brings the Foregjo Actions running experience much more closely into line with GitHub's environment (VM, rather than container). We hope to contribute this back shortly, but also drop me a message if this is of interest.
2) We're working up a proposal[1] to add environments and variable groups to Forgejo Actions. This is something we expect to need for some upcoming compliance requirements.
I really like Forgejo as a project, and I've found the community to be very welcoming. I'm really hoping to see it grow and flourish :D
[0]: https://lithus.eu, adam@
[1]: https://codeberg.org/forgejo/discussions/issues/440
PS. We are also looking at offering this as a managed service to our clients.
Re: GitHub is down again
#299You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history .
I'm happy that they're being transparent about it. There's no good way to take downtime, but at least they don't try to cover it up. We can adjust and they'll make it better. I'm sure a retro is on its way it's been quite the bumpy month.
Re: GitHub is down again
#300Earlier quoted context omitted.
That's probably partly why things have got increasingly flaky - until they finish there'll be constant background cognitive load and surface area for bugs from the fact everything (especially the data) is half-migrated
You'd think so, and we don't know about today's incident yet, but recent Github incidents have been attributed specifically to Azure, and Azure itself has had a lot of downtime recently that lasts for many hours.
True, the even simpler explanation is what they've migrated to is itself just unreliable