21–30 of 35 posts
Do we really need a new thread every time GH is down for 5 minutes? Also, please use GitLab.
What prevents GitLab from going down like GitHub?
Update: Yeah, maybe if we run an own GitLab instance in our corporate network.
Update update: Hmm, there seem to be outages in February, March and April, too. Source: https://news.ycombinator.com/item?id=11736331
Do we really need a new thread every time GH is down for 5 minutes? Also, please use GitLab.
Do we really need a new thread every time GH is down for 5 minutes? Also, please use GitLab.
> Also, please use GitLab.
and you can't just say "use xyz".
Ir works for me
I have the feeling that this is happening more and more these days. And it's a mayor problem when a large part of your infrastructure is depending on services like Github (composer, etc.)
It's kind of ironic when one realizes that one of the major design goals of git was to be distributed, to reduce dependency on a single point of failure.
Earlier quoted context omitted.
From https://status.github.com/graphs/past_month Past Month: APP SERVER AVAILABILITY 99.1701%
Being down for the equivalent of 3 days/year isn't great.
My favourite part of this is the "All systems operational" in green at the top. Yet, all systems are clearly not operational.
Earlier quoted context omitted.
It's kind of ironic when one realizes that one of the major design goals of git was to be distributed, to reduce dependency on a single point of failure.
GitHub isn't really a single point of failure. You could easily keep working on your branches and/or forks and re-sync once the server is back up.
Earlier quoted context omitted.
GitHub isn't really a single point of failure. You could easily keep working on your branches and/or forks and re-sync once the server is back up.
That's definitely true, but PRs, comments and bug reports are not distributed, nor are many bridges between Github and external tools (issue trackers like JIRA/Trello, build-servers). This might seem pedantic, but it creates an asymmetry: commits and branches distributed, as opposed to PRs and comments.