"Major service outage"
11–20 of 60 posts
Re: "Major service outage"
#12Re: "Major service outage"
#13Re: "Major service outage"
#14Re: "Major service outage"
#15Earlier quoted context omitted.
I've found it somewhat odd how, although advocating the use of a decentralized version control system, much of the git community has ended up heavily centralized on GitHub.
It is a distributed system. You still have to have shared remotes in order to integrate branches.
You're also not limited to one shared repo by any means, so even synchronization between multiple developers can continue when github is down. To avoid problems it's of course a good idea when one of the repos is a "master", and if using a secondary repo for synchronization when the master is down, you'll probably want to switch to unique temporary branches for the purpose.
Re: "Major service outage"
#16Github is great, they're working on some serious problems, and every service has downtime. But this is getting pretty serious. This is the 3rd time in these last few weeks there has been a "significant service outage" So much of a typical dev workflow is based around github, but more importantly a lot of new package managers use github as a base. Not being able to pull dependencies is a fairly big problem. I will con…
I wouldn't call this "building around" GitHub. Git's nature promotes this kind of thing.
Re: "Major service outage"
#17If they keep this up I'm gonna have to buy github-enterprise! wait a minute...