@@ -31,7 +31,7 @@ The instructions below are for command line use of git.
31
31
on the fork's page on Github.
32
32
33
33
34
- 3 . Next, make a local branch on your computer in your working repository
34
+ 2 . Next, make a local branch on your computer in your working repository
35
35
with the proposed code changes. Here are the command lines
36
36
(substitute the user, branch, and fork names we found above):
37
37
@@ -48,14 +48,14 @@ The instructions below are for command line use of git.
48
48
```
49
49
50
50
51
- 4 . This has made a local branch named
51
+ 3 . This has made a local branch named
52
52
`contributorusername-contributor_branch_name`. Go ahead and test
53
53
and review the PR and make code edits and new commits to your
54
54
local branch as needed.
55
55
56
56
57
57
58
- 5 . In order to push the changes to the contributor's fork (and the PR
58
+ 4 . In order to push the changes to the contributor's fork (and the PR
59
59
on Github from the fork), you will specify the upstream to be the
60
60
contributor's fork:
61
61
@@ -93,7 +93,7 @@ The instructions below are for command line use of git.
93
93
```
94
94
95
95
96
- 6 . Now once you are finished with your code changes, first commit them to
96
+ 5 . Now once you are finished with your code changes, first commit them to
97
97
the local branch (named
98
98
`contributorusername-contributor_branch_name`).
99
99
@@ -106,7 +106,7 @@ The instructions below are for command line use of git.
106
106
*NOTE: If you encounter a permissions error, it is possible that the external
107
107
contributor didn't grant access for collaboration on the branch.*
108
108
109
- 7 . Confirm that you can see the changes on the Github website for the PR.
109
+ 6 . Confirm that you can see the changes on the Github website for the PR.
110
110
111
111
112
112
---
0 commit comments