Live data from Hacker News

GitHub was down again

githubstatus.com

81–90 of 125 posts

Re: GitHub was down again

#81
post #71

What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.

git clone ... which you already have

git remote add originFoo URL

git push --all originFoo

There are other flags like mirror but never used them.

Source: https://git-scm.com/docs/git-push

Re: GitHub was down again

#82
post #71

What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.

Other answers talking about using git features are assuming that you don't care about Wiki/PRs/Issues/Labels/etc that are GitHub metadata not part of your repo history.

But GitLab does have feature support for extensive importing and mirroring. https://docs.gitlab.com/ee/user/project/import/github.html (Import your project from GitHub to GitLab) has a section on project mirroring.

Re: GitHub was down again

#83
post #80
post #77

Earlier quoted context omitted.

Run git on a personal server[1]? It's not as complicated as you might think. Probably much more usable to setup gitlab. Then set up the alternative remote on your repos. [1] https://www.linux.com/training-tutorials/how-run-your-own-gi...

I posted this on another thread. If you only want the commits, something like this works, ssh user@git.example.com mkdir project-1.git cd project-1.git git init —-bare exit git remote add alternate user@git.example.com:project-1.git All you need is SSH

I use it also that way. Gitlab does the same if you use ssh. They provide hooks on init so that gitlab knows if something happens.

Re: GitHub was down again

#84
post #80
post #77

Earlier quoted context omitted.

Run git on a personal server[1]? It's not as complicated as you might think. Probably much more usable to setup gitlab. Then set up the alternative remote on your repos. [1] https://www.linux.com/training-tutorials/how-run-your-own-gi...

I posted this on another thread. If you only want the commits, something like this works, ssh user@git.example.com mkdir project-1.git cd project-1.git git init —-bare exit git remote add alternate user@git.example.com:project-1.git All you need is SSH

All you need to get all commits and all tags/branches:

  git clone --mirror https://github.com/you/repo
Push those to another server:

  git remote add new https://gitlab.com/you/repo
  git push --mirror new

Re: GitHub was down again

#85
post #77
post #71

What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.

Run git on a personal server[1]? It's not as complicated as you might think. Probably much more usable to setup gitlab. Then set up the alternative remote on your repos. [1] https://www.linux.com/training-tutorials/how-run-your-own-gi...

That's fine for your code repository.

However git has more: - Bug tickets - PR - Wiki - many projects use their githubpages as primary homepage - newly GitHub actions

And then: Often collaborators are only known and identified by their GitHub handle. Running an own server requires some mechanism to identify them again and creating a way to handle their access credentials (ssh key etc.)

Moving a mildly successful project isn't easy. Good if more people plan for that eventuality, even if they stay on GH for the time being.

Re: GitHub was down again

#86
Do I have to repeat this over and over again? If these non-profit open-source projects [0] are able to self-host a git solution like GitLab, Gitea, cgit or Phabricator instance somewhere, surely your team or open-source project can too.

Even a self-hosted GH Enterprise would suffice for some businesses but this would be overkill for others. I even see the Wireguard author using his own creation (cgit) to self-host on his own git solution for years. [1]

This is problematic since many JS/TS, Go and Rust packages are on GitHub, which many developers rely on. Thus, it would be risky to think about tieing open-source project to (GitHub Actions, Apps, etc).

[0] https://news.ycombinator.com/item?id=23818020

[1] https://git.zx2c4.com

Re: GitHub was down again

#87

Earlier quoted context omitted.

What's the point in having a status page if it's a political artifact? In that case, it serves zero customer value.

It’s still an indicator that “no you’re not crazy, we’re having issues on our end” but not a foolproof one. It’s kind of sad that twitter is usually the best place to confirm an outage as it begins, rather than the software providers themselves. I assume if they actually exposed global availability metrics in most cases it would not look as good as they would want it to

Down detector is based on twitter complaints and is pretty damn accurate.

Re: GitHub was down again

#88
post #4
post #3

GitHub used to have a pretty cool status page, with all kinds of real time graphs. Does anyone know what happened to it? Since it makes me really sad that this status page is a plain lie, I had to visit HN to get the confirmation that they are having issues again, and that it just wasn't only me.

I read an article about it, look for "status page evolution" https://nimbleindustries.io/2020/06/04/has-github-been-down-...

> But that could be all a part of coordinated effort to be more transparent about their service status, an effort that should be applauded.

Microsoft could be pushing for transparency. Or people are more relaxed about transparency now that GitHub has its exit. How long did GitHub know they were looking to be acquired? Maybe this analysis should look at a longer time interval..

Re: GitHub was down again

#89
post #86

Do I have to repeat this over and over again? If these non-profit open-source projects [0] are able to self-host a git solution like GitLab, Gitea, cgit or Phabricator instance somewhere, surely your team or open-source project can too. Even a self-hosted GH Enterprise would suffice for some businesses but this would be overkill for others. I even see the Wireguard author using his own creation (cgit) to self-host on…

Wait, will you really repeat this until you no longer see a "github down" link on HN frontpage?

That is dedication.

Re: GitHub was down again

#90
post #17

I was seeing PRs failing to update & webhooks failing to trigger upon pushing code for 30 minutes before GH's status page acknowledged anything. I'm surprised they don't have monitoring in place that would catch webhooks failing within minutes of the failure beginning.

At large bureaucratic organisations there's often political implications of changing the official status, so often it lags behind reality until it cannot be swept under the rug anymore Not saying it's right, just an observation

3 words: Service Level Agreement

I've caught a big cloud provider not reporting a degraded service, I assume they knew but politics and $ come in and it's easier to just gaslight everyone. I get it, but my frustration is worth loosing a trailing 9.

I think there should be some 3rd party continuously testing APIs. Degraded states are downtime!

Post reply on HN