It's getting to where we should just post when it's working fine, to reduce noise.
Incident with Github.com [resolved]
21–30 of 1001 posts
Re: Incident with Github.com [resolved]
#22We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?" No idea if/when we decide to pull that bandaid but I think once we can't merge a hot fix into main because of GH being down, it'll be a big org push to replace it. What's everyone else using? Self hosted Gitlab? Gitea?
Self hosted Gitea
Re: Incident with Github.com [resolved]
#23Which AI model is it this time?
Re: Incident with Github.com [resolved]
#24Welp, workday over in Europe early!
Who are you kidding, nobody has been in since the start of August!
Re: Incident with Github.com [resolved]
#25Yes, in India.
Re: Incident with Github.com [resolved]
#26If you are required to use a Microsoft tool is Azure DevOps now a better choice? Our Azure hosted instance rarely (if ever) has had an outage that effects our ability to work.
Re: Incident with Github.com [resolved]
#27Can anyone shed some light why GitHub is having so many problems lately?
Re: Incident with Github.com [resolved]
#28As I said 4 days ago GitHub is in chronic operational decline which is killing trust in hosting repositories [0]
You can use as many AI agents as you want (it won’t solve the problem), but with that many outages ever since getting bought by Microsoft, it is more than enough time to give them to change. They don’t care and there is no CEO of GitHub to help either.
A self hosted instance would have much better uptime than GitHub and GitHub Actions at this point as I predicted 6 years ago. [1]
Re: Incident with Github.com [resolved]
#29I had a lot of goodwill for GitHub but I think today is the tipping point.
Looking at a unicorn page, I feel this lingering hope that it's transient (like it usually was in the old days) but my mind reassures me it's probably going to be a long full outage again.
The hope is dead.
Re: Incident with Github.com [resolved]
#30We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?" No idea if/when we decide to pull that bandaid but I think once we can't merge a hot fix into main because of GH being down, it'll be a big org push to replace it. What's everyone else using? Self hosted Gitlab? Gitea?
> We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?"
Did you have the conversation "do we need to move from $whatever CI/CD to GitHub Actions?" beforehand? What were the arguments in favour?