Git is a DVCS.

Github happens to be hosting repos, but it is just a remote that one pushes to.

You can have multiple remotes and push to them.

So, a project can have a couple remotes to push/pull to/from.

e.g. I have a couple things going on now where one company uses github private repos and another is on bitbucket.

No issue adding both remotes and synching both repos.

One can also have its own Gitlab, http://gogs.io, or whatever git hosting provider or your own git daemon (https://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon).

The main thing is then the issues list and PR flow which is not a Git thing per se.

So, two things here:

- convince to use git (which is IMHO a no-brainer vs SVN)
- convince to use github (which is a good proposal, but bitbucket has nice advantages too)

The greatest advantage is that everyone having cloned the repo has the full history (provided one does a fetch --all for getting all branches).

So, it would be close to impossible to lose the code even if providers go down.

For command line users, check out tig (http://jonas.nitro.dk/tig/manual.html) which is really a great ncurses based git client.

Can see about everything very easily.

For some git power, check also:

git mergetool
git difftool

which allow do diff/merge branches without trouble.

Phil

Phil

��

On Thu, Dec 17, 2015 at 9:37 PM, Peter Uhn��k <i.uhnak@gmail.com> wrote:
> well, googlecode closed didn't it?
> and it was not a small affair either

And all you needed was to click on a button and magically it was on github.

But this is very different scenario to what the worry is about.
When GitHub one day closes GoogleCode style, then there is nothing to
worry about, because there will be time to move to something better.
The worry is when it is sudden without time.

Peter