Maybe we should start posting av story when GitHub has been fine for some time instead of posting every incident
Incident with Pull Requests, Issues, Git Operations and API Requests
11–20 of 221 posts
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#12https://isgithubcooked.com Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.
Name one thing Microsoft didn't run into the ground post-acquisition
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#13They may have gotten down to only 2 nines on most of their services, but at least the LLM is still running at full power! must increase value for shareholders
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#14Are they running paid marketing campaigns for Gitlab ?
I'd consider self-hosting GitHub Enterprise before putting my team through the pain of Gitlab.
How is it painful to use GitLab? Curious, as a user of both, I find them both nice. I like GitLab CI/CD more than I do GHA, but that's personal preference/bias more than anything objective.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#15git is supposed to be decentralized.
maybe it's time to revert back to the central idea of git & not centralize around a particular provider.
for issues - mailing list will do. you can always slap a beautiful ui if you want to or a tui (as is the fad) these days.
actions can also be decentralized via an API spec & webhooks.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#16https://isgithubcooked.com Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.
Name one thing Microsoft didn't run into the ground post-acquisition
GH was acquired by microsoft some eight years ago. It has been working quite well until recently.
People may have had complaints about functionality, features, commercial issues, but the thing used to at least have a decent uptime until recently.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#17Before clicking, I assumed this was going to be a write-up of the one from a few days ago instead of an entirely new incident.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#18is it me or ever since AI coding became the norm, there have been way more outages with otherwise reliable services?
I get downtime on Supabase every few weeks. Even Cloudflare. And now Github
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#19Tried to do a git push - it succeeded after 3 mins. Then I wanted to open a PR and it failed with a 500 error.
Facepalmed and decided that this is it for today.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#20Yesterday my CI runs wouldn't even be created because Actions was eating shit, and today my CI runs get created but fail because the API is eating shit. Fun.