First you follow the instructions for Making your own copy (fork) of DIPY. Clone your fork to the local computer with Investigate. Change directory to your new repo: This tells you that you are currently on the Now you want to connect to the upstream dipy github repository, so
you can merge in changes from trunk. Note that we’ve used Just for your own satisfaction, show yourself that you now have a new
‘remote’, with Set up your fork
Overview
git clone git@github.com:your-user-name/dipy.git
cd dipy
git remote add upstream git://github.com/dipy/dipy.git
In detail
Clone your fork
git clone
git@github.com:your-user-name/dipy.git
cd dipy
. Then
git branch -a
to show you all branches. You’ll get something
like:* master
remotes/origin/master
master
branch, and
that you also have a remote
connection to origin/master
.
What remote repository is remote/origin
? Try git remote -v
to
see the URLs for the remote. They will point to your github fork.Linking your repository to the upstream repo
cd dipy
git remote add upstream git://github.com/dipy/dipy.git
upstream
here is just the arbitrary name we’re using to refer to the
main dipy repository at dipy github.git://
for the URL rather than git@
. The
git://
URL is read only. This means we that we can’t accidentally
(or deliberately) write to the upstream repo, and we are only going to
use it to merge into our own code.git remote -v show
, giving you something like:upstream git://github.com/dipy/dipy.git (fetch)
upstream git://github.com/dipy/dipy.git (push)
origin git@github.com:your-user-name/dipy.git (fetch)
origin git@github.com:your-user-name/dipy.git (push)