8000 Merge pull request #8205 from rgommers/https-clone · numpy/numpy@e7d6f36 · GitHub
[go: up one dir, main page]

Skip to content

Commit e7d6f36

Browse files
authored
Merge pull request #8205 from rgommers/https-clone
DOC: change development instructions from SSH to HTTPS access.
2 parents 0e4de36 + 092d884 commit e7d6f36

File tree

1 file changed

+37
-5
lines changed

1 file changed

+37
-5
lines changed

doc/source/dev/gitwash/development_setup.rst

Lines changed: 37 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Overview
6060

6161
::
6262

63-
git clone git@github.com:your-user-name/numpy.git
63+
git clone https://github.com/your-user-name/numpy.git
6464
cd numpy
6565
git remote add upstream git://github.com/numpy/numpy.git
6666

@@ -71,7 +71,7 @@ Clone your fork
7171
---------------
7272

7373
#. Clone your fork to the local computer with ``git clone
74-
git@github.com:your-user-name/numpy.git``
74+
https://github.com/your-user-name/numpy.git``
7575
#. Investigate. Change directory to your new repo: ``cd numpy``. Then
7676
``git branch -a`` to show you all branches. You'll get something
7777
like::
@@ -100,7 +100,7 @@ Linking your repository to the upstream repo
100100
``upstream`` here is just the arbitrary name we're using to refer to the
101101
main NumPy_ repository at `NumPy github`_.
102102

103-
Note that we've used ``git://`` for the URL rather than ``git@``. The
103+
Note that we've used ``git://`` for the URL rather than ``https://``. The
104104
``git://`` URL is read only. This means we that we can't accidentally
105105
(or deliberately) write to the upstream repo, and we are only going to
106106
use it to merge into our own code.
@@ -110,7 +110,39 @@ Just for your own satisfaction, show yourself that you now have a new
110110

111111
upstream git://github.com/numpy/numpy.git (fetch)
112112
upstream git://github.com/numpy/numpy.git (push)
113-
origin git@github.com:your-user-name/numpy.git (fetch)
114-
origin git@github.com:your-user-name/numpy.git (push)
113+
origin https://github.com/your-user-name/numpy.git (fetch)
114+
origin https://github.com/your-user-name/numpy.git (push)
115+
116+
To keep in sync with changes in NumPy, you want to set up your repository
117+
so it pulls from ``upstream`` by default. This can be done with::
118+
119+
git config branch.master.remote upstream
120+
git config branch.master.merge refs/heads/master
121+
122+
You may also want to have easy access to all pull requests sent to the
123+
NumPy repository::
124+
125+
git config --add remote.upstream.fetch '+refs/pull//head:refs/remotes/upstream/pr/'
126+
127+
Your config file should now look something like (from
128+
``$ cat .git/config``)::
129+
130+
[core]
131+
repositoryformatversion = 0
132+
filemode = true
133+
bare = false
134+
logallrefupdates = true
135+
ignorecase = true
136+
precomposeunicode = false
137+
[remote "origin"]
138+
url = https://github.com/your-user-name/numpy.git
139+
fetch = +refs/heads/*:refs/remotes/origin/*
140+
[remote "upstream"]
141+
url = git://github.com/numpy/numpy.git
142+
fetch = +refs/heads/*:refs/remotes/upstream/*
143+
fetch = +refs/pull/*/head:refs/remotes/upstream/pr/*
144+
[branch "master"]
145+
remote = upstream
146+
merge = refs/heads/master
115147

116148
.. include:: git_links.inc

0 commit comments

Comments
 (0)
0