Earlier quoted context omitted.
Microsoft is also convinced that its works are a net benefit for humanity, so I would take that with a grain of salt.
I think it would be pretty hard to argue against that point of view, at least thus far. If DOS/Windows hadn't become the dominant OS someone would have, and a whole generation of engineers cut their teeth on their parents' windows PCs.
GitHub: Git operation failures
171–180 of 335 posts
Re: GitHub: Git operation failures
#172We live in a house of cards. I hope that eventually people in power realize this. However, their incentive structures do not seem to be a forcing function for that eventuality. I have been thinking about this a lot lately. What would be a tweak that might improve this situation?
Re: GitHub: Git operation failures
#173FYI 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.
FYI in an emergency you can `git push` to and `git pull` from any SSH-capable host without the need to use GitHub.
They done borked it good.
Re: GitHub: Git operation failures
#174FYI 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
#175Re: GitHub: Git operation failures
#176I have a serious question, not trying to start a flame war. A. Are these major issues with cloud/SaaS tools becoming more common, or is it just that they get a lot more coverage now? It seems like we see major issues across AWS, GCP, Azure, Github, etc. at least monthly now and I don't remember that being the case in the past. B. If it's becoming more common, what are the reasons? I can think of a few, but I don't kn…
> A. Are these major issues with cloud/SaaS tools becoming more common, or is it just that they get a lot more coverage now? It seems like we see major issues across AWS, GCP, Azure, Github, etc. at least monthly now and I don't remember that being the case in the past. FWIW Microsoft is convinced moving Github to Azure will fix these outages
Re: GitHub: Git operation failures
#177Earlier quoted context omitted.
You just lose the "hub" of connecting others and providing a way to collaborate with others with rich discussions.
All of those sound achievable by email, which, coincidently, is also decentralized.
It's more work and slower. I'm convinced half of the reason they keep it that way is because the barrier to entry is higher and it scares contributors away.
Re: GitHub: Git operation failures
#178GitHub is pretty easily the most unreliable service I've used in the past five years. Is GitLab better in this regard? At this point my trust in GitHub is essentially zero - they don't deserve my money any longer.
We've been self hosting GitLab for 5 years and it's the most reliable service in our organization. We haven't had a single outage. We use Gitlab CI and security scanning extensively.
Re: GitHub: Git operation failures
#179Re: GitHub: Git operation failures
#180Earlier quoted context omitted.
FYI in an emergency you can `git push` to and `git pull` from any SSH-capable host without the need to use GitHub.
I'm actually getting "ERROR: no healthy upstream" on `git pull`. They done borked it good.