GitHub banned us without notice – Is Microsoft the risk we didn’t consider?
medium.com
medium.com
To be honest, it seems like a fairly simple mistake that was cleaned up within 48 hours. Certainly a pain in the ass, but these things happen.
However, the author does point out several good practices:
* Don't host your code only in one place
* Don't host your services only in one provider
* Don't host your backups only in one provider
I suppose you could argue the second one, but the other two are important to follow.
If it's worth a lot of time and cannot be replaced easily, back it up.
[0] https://www.recode.net/2017/3/2/14792636/amazon-aws-internet...
It seems like it could run afoul of anti-trust laws if you are functioning as one company in a situation where the merger might not get government approval.
I also wonder if it could cause liability issues because, until the deal closes, you are obligated to do what your current owners want you to, not your hypothetical (but probable) future owners. Especially if you are a public company and those owners are shareholders that you probably have certain legal obligations toward.
There may be some unspoken preference towards MS or something, but, if so, it's not super evident. And given the pre-existing relationship between devs at both companies, it could also just have been there beforehand. It would be pretty impossible to know.
They also don't have any links to their GitHub pages on their site. This isn't how organizations normally use GitHub. One suspects they're just using it as a CDN without engaging with any of the coding or social features. Perhaps GitHub has some sort of trigger when particular resources get requested over and over without any referer? Why not just use GitHub normally? Failing that, why not just use a CDN?