@@ -35,8 +35,8 @@ Retrieve the latest version of the code
35
35
=======================================
36
36
37
37
Now that your fork of the repository lives under your GitHub username, you can
38
- retrieve thelatest sources with one of the following commands (where your
39
- should replace ``<your-username> `` with your GitHub username):
38
+ retrieve themost recent version of the source code with one of the following
39
+ commands ( replace ``<your-username> `` with your GitHub username):
40
40
41
41
..tab-set ::
42
42
@@ -59,14 +59,12 @@ should replace ``<your-username>`` with your GitHub username):
59
59
60
60
61
61
This will place the sources in a directory:file: `matplotlib ` below your
62
- current working directory and setup the ``origin ``remote to point to your own
63
- fork. Change into this directory before continuing::
62
+ current working directory and set theremote name ``origin `` to point to your
63
+ fork. Change into this directory before continuing::
64
64
65
65
cd matplotlib
66
66
67
- Now set up the ``upstream `` remote to point to the Matplotlib main repository,
68
- so that you can access the latest changes there (see also `Managing remote repositories
69
- <https://docs.github.com/en/get-started/getting-started-with-git/managing-remote-repositories> `__.):
67
+ Now set the remote name ``upstream `` to point to the Matplotlib main repository:
70
68
71
69
..tab-set ::
72
70
@@ -82,18 +80,25 @@ so that you can access the latest changes there (see also `Managing remote repos
82
80
83
81
git remote add upstream git@github.com:matplotlib/matplotlib.git
84
82
85
- ..note ::
83
+ You can now use ``upstream `` to retrieve the most current snapshot of the source
84
+ code, as described in:ref: `development-workflow `.
86
85
87
- For more information on ``git `` and ``GitHub ``, check the following resources.
86
+ ..dropdown ::Additional ``git`` and ``GitHub`` resources
87
+ :color: info
88
+ :open:
89
+
90
+ For more information on ``git `` and ``GitHub ``, see:
91
+
92
+ * `Git documentation <https://git-scm.com/doc >`_
93
+ * `GitHub-Contributing to a Project <https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project >`_
94
+ * `GitHub Skills <https://skills.github.com/ >`_
95
+ *:ref: `using-git `
96
+ *:ref: `git-resources `
97
+ * `Installing git <https://git-scm.com/book/en/v2/Getting-Started-Installing-Git >`_
98
+ * `Managing remote repositories <https://docs.github.com/en/get-started/getting-started-with-git/managing-remote-repositories >`_
99
+ * https://tacaswell.github.io/think-like-git.html
100
+ * https://tom.preston-werner.com/2009/05/19/the-git-parable.html
88
101
89
- * `Git documentation <https://git-scm.com/doc >`_
90
- * `GitHub-Contributing to a Project <https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project >`_
91
- * `GitHub Skills <https://skills.github.com/ >`_
92
- *:ref: `using-git `
93
- *:ref: `git-resources `
94
- * `Installing git <https://git-scm.com/book/en/v2/Getting-Started-Installing-Git >`_
95
- * https://tacaswell.github.io/think-like-git.html
96
- * https://tom.preston-werner.com/2009/05/19/the-git-parable.html
97
102
98
103
.. _dev-environment :
99
104