ERROR: no healthy upstream fatal: Could not read from remote repository.
GitHub: Git operation failures
31–40 of 335 posts
Re: GitHub: Git operation failures
#32Re: GitHub: Git operation failures
#33Re: GitHub: Git operation failures
#34FYI in an emergency you can edit files directly on Github without the need to use git. Edit: ugh... if you rely on GH Actions for workflows though actions/checkout@v4 is also currently experiencing the git issues, so no dice if you depend on that.
Re: GitHub: Git operation failures
#35Earlier quoted context omitted.
Eh, the lesson from us-east-1 outage is that you should cling to the big ones instead. You get the convenience + nobody gets mad at you over the failure.
Everything will have periods of unreliability. The only solution is to be multi-everything (multi-provider for most things), but the costs for that are quite high and hard to see the value in that.
Re: GitHub: Git operation failures
#36Re: GitHub: Git operation failures
#37Why are there outages everywhere all the time now? AWS, Azure, GitHub, Cloudflare, etc. Is this the result of "vibe coding"? Because before "vibe coding", I don't remember having this many outages around the clock. Just saying.
"Why do we need so many people to keep things running!?! We never have downtime!!"