Sounds like we have the basics of an oscillating system now!

I wonder what it's resonant frequency is.

Is Github free of problems? I don't know. Maybe an option would be hosting gitea and sync projects to an online account.

That, or the massive lightning that's going through the region, (due to the heatwave). Since it's quite late at night, heat wouldn't be my first guess.

I'll put my money on AI software contributions...

I use it to sync projects that I mainly host on Codeberg up to GitHub. It was a "set it and forget it" kind of thing.

I am using it to backup my public and private repositories to Github and it's effortless, indeed. I am using ssh protocol and a read/write deployment key. Also, I anticipated `git push --force` could be an issue, it's not.

Codeberg runs open source Forgejo, and you could on-prem that too (for no license cost), if it suits your needs.

GitLab is more powerful in some ways, but early startups might want to look at Forgejo first.

This seems like a weird comment since Codeberg is only for open source projects, you literally cannot use it for private code. On-prem Forgejo would be the equivalent to on-prem GitLab, both of which are unrelated to this outage.

On perm Gitlab has a ton of problems too.

Nowadays, these code forges have also become a centralized place for issue tracking, kanban boards, wiki editing and, specially, as CI/CD servers, in the case of GitHub Actions, which are, sometimes, the only for you to deploy software to package repositories. The same limitations apply to GitLab CI or Codeberg's Forgejo Runners/Woodpecker.

Whenever GitLab, Codeberg, BitBucket and, mostly, GitHub goes down, a lot of the software and websites you use can't be updated, including dependencies of your software that you're pulling from npm, for instance.

Finally, companies use code forges mostly for the ease of doing code reviews through Pull Requests/Merge Requests. Developers rarely, if ever, actually merge branches locally, before having it reviewed by peers in one of these code forges.

Git is a DVCS, but many companies have a build server/cluster that depends on Github or Codeberg being available.

Teams I've worked on for the last several decades aim to push 10-20 builds per day to external alpha testers, so any downtime in Github is going to be an impediment.

Do you not spend much time writing and discussing issues or reviewing code?

From what I understand, Codeberg is a pretty small nonprofit group.

3 physical servers can power a ton of requests.

Codeberg is smaller than GitHub and, you know, Go is slightly more efficient than Ruby :)

That's because most of what you can see of a Codeberg is actually underwater.

Does Forgejo count?

Comaps too.

Consider that maybe you haven’t heard of all the things that HN readers find interesting.

There are a couple of very vocal people who are generally liked here who wrote angry blog posts about moving from Github to Codeberg.

This is why it's getting traction.