Should have self hosted.
GitHub having issues [resolved]
61–70 of 150 posts
Re: GitHub having issues [resolved]
#62I would so very much love to see GitHub switch gears from building stuff like Copilot etc and focus on availability
Re: GitHub having issues [resolved]
#63How many 9s is GitHub at now? 2?
Re: GitHub having issues [resolved]
#64Earlier quoted context omitted.
Top-down mandates to use AI as much as possible, and to rip up their infrastructure and move everything to Azure. https://www.windowscentral.com/microsoft/using-ai-is-no-long... https://thenewstack.io/github-will-prioritize-migrating-to-a...
This is very worrying if their mandate doesn't include quality control.
Re: GitHub having issues [resolved]
#65I swear this is my fault. I can go weeks without doing infra work. Github does fine, I don't see any hiccups, status page is all green. But the day comes that I need to tweak a deploy flow, or update our testing infra and about halfway through the task I take the whole thing down. It's gotten to the point where when there's an outage I'm the first person people ask what I'm doing...and it's pretty dang consistent....
Re: GitHub having issues [resolved]
#66If anyone is using Github professionally and pays for github actions or any github product, respectfully, why?
You can switch to a VPS provider and self host gitea/forejo in less time than you might think and pay a fraction of a fraction than you might pay now.
The point becomes more moot because github is used by developers and devs are so so much more likely to be able to spin up a vps and run forejo and run terminal. I don't quite understand the point.
There are ways to run github actions in forejo as well iirc even on locally hosted which uses https://github.com/nektos/act under the hood.
People, the time where you spent hundreds of thousands of dollars and expected basic service and no service outage issues is over.
What you are gonna get is service outage issues and lock-ins. Also, your open source project is getting trained on by the parent company of the said git provider.
PS: But if you do end up using Gitea/forejo. Please donate to Codeberg/forejo/gitea (Gitea is a company tho whereas Codeberg is non profit). I think that donating 1k$ to Codeberg would be infinitely better than paying 10k$ or 100k$ worth to Github.
Re: GitHub having issues [resolved]
#67I swear this is my fault. I can go weeks without doing infra work. Github does fine, I don't see any hiccups, status page is all green. But the day comes that I need to tweak a deploy flow, or update our testing infra and about halfway through the task I take the whole thing down. It's gotten to the point where when there's an outage I'm the first person people ask what I'm doing...and it's pretty dang consistent....
Re: GitHub having issues [resolved]
#68The appearance of a thread here is so consistent that HN needs a black-bar style indicator for GH outages that points to it.
Re: GitHub having issues [resolved]
#69codeberg might be a little slower on git cli, but at least it's not becoming a weekly 'URL returned error: 500' situation...
Re: GitHub having issues [resolved]
#70codeberg might be a little slower on git cli, but at least it's not becoming a weekly 'URL returned error: 500' situation...
I rarely successfully get Codeberg URLs to load. Which is sad because I actually would very much like to recommend it but I find it unreliable as a source. That being said, GitHub is Microsoft now, known for that Microsoft 360 uptime.
Actually here you go, I have pasted the matrix link to their community, hope it helps https://matrix.to/#/#codeberg-space:matrix.org