I saw some comments on reddit which highlighted a pretty serious problem - many orgs rely on github as a fully integrated CD platform, with everything from code hosting, to running CI hooks, to pushing to staging or prod.<p>It seems very unwise to have essentially your whole deployment process manager in the hands of an entity which you don't only have no control over, but which has regularly been targeted in attacks by nation-state-level actors because of their role as a code hosting platform.<p>EDIT: GH hasn't been targeted regularly, but it has been so historically, so this is a plausible thing which might happen again.
Yeah, we're still facing issues with, erm, Github issues.<p>Also, while they haven't updated this blog post for a while, their status page has been very up-to-date and informative: <a href="https://status.github.com/messages" rel="nofollow">https://status.github.com/messages</a>
On the plus side, this disastrous calamity by Github really made me try out Gitlab and in the process, I will now set-up a second remote on my repo's:<p><a href="https://stackoverflow.com/questions/11690709/can-a-project-have-multiple-origins" rel="nofollow">https://stackoverflow.com/questions/11690709/can-a-project-h...</a><p><pre><code> Quoted:
"Try adding a remote called "github" instead:
$ git remote add github
https://github.com/Company_Name/repository_name.git
# push master to github
$ git push github master
# Push my-branch to github and set it to track github/my-branch
$ git push -u github my-branch
# Make some existing branch track github instead of origin
$ git branch --set-upstream other-branch github/other-branch"
</code></pre>
Actually, I don't know why I pay for Github private repo's.. I might as well set-up two origins, one at Gitlab and one at Bitbucket, for all my privates. Then keep Github as a public front-facing portal.
Ugh I detest the term " abundance of caution " as used in that message. Weasel words designed to stop you thinking about the problem as who wouldn't want them to be overly cautious
> During this time, information displayed on GitHub.com is likely to appear out of date;<p>if the new data is not presented, users will typically retry which may result in duplicated new content.
Wow, is this still going on? I noticed this yesterday and figured it would be fixed in a few hours, but [GitHub's status page][1] is still showing red. Is this the longest outage GitHub has had?<p>[1]: <a href="https://status.github.com/messages" rel="nofollow">https://status.github.com/messages</a>
This incident report tells very little. I hope they release what actually happened and how it affected their services. And how they are going to avoid it in the future.
Almost any issue can be publicly described as: stuff broke because of network.
Something that struck me yesterday as this started, is that Github isn’t really just a dvcs hosting solution, Github is a social network.<p>It’s easy to change the remote origin of a git repository. It’s not hard to migrate a project to Gitlab etc, and duplicate all the technical features of Github.<p>What’s really hard is replacing the social graph. If you’re a large project with a lot of contributors, onboarding everyone is not going to be easy. About as easy as convincing all your friends to stop using Facebook.
> Further, this incident only impacted website metadata stored in our MySQL databases, such as issues and pull requests.<p>Basically the only things I was going to do on Github today :)
Why bother telling people five incorrect estimates for service recovery?<p><a href="https://twitter.com/sneakdotberlin/status/1054345379716558849" rel="nofollow">https://twitter.com/sneakdotberlin/status/105434537971655884...</a><p>After one or two wrong guesses it just shows that you’re making it up.
GitHub also silently published a private repo of mine this week. I checked audit logs for both the owner user and the org and it didn’t show a permissions change anywhere.<p>Netlify has caused me to stop using GitHub Pages and between the clownshoes outage reports and the security issue I am now a GitLab user.<p>This is GitHub’s jump the shark episode. :(
As I rearrange today's todo list, I recall wishing that I'd used the Microsoft purchase event to encourage folks to increase their familiarity with gitlab. So I now note:<p><a href="https://gitlab.com/explore/projects" rel="nofollow">https://gitlab.com/explore/projects</a> is a live feed of project activity, suitable for code surfing. It also sorts by stars and trending.
Lets do a quick back of the envelope calculation:<p>Github reports 28,337,706 users by 2018-06-05 [1]. Lets assume 50% of these are active. Lets also assume that, due to the unavailability of GH, around 2 usable hours per developer are lost. Another assumption is that each developer contributes around 50 US$ per hour.<p>This means, this outage has cost us users: (28337706 * .5 * 2 * 50) = 1.351 billion US$.<p>Perhaps not use MySQL for such critical systems?<p>[1] <a href="https://github.com/search?q=type:user&type=Users" rel="nofollow">https://github.com/search?q=type:user&type=Users</a>
GitHub team seems to be <i>VERY</i> unprofessional. 15 hour outage means ~99.82% availability which is extremely bad. 9 hours ago they also told that they would fix the problem within 2 hours... still not fixed!!!