@@ -31,7 +31,7 @@ The instructions below are for command line use of git.
3131 on the fork's page on Github.
3232
3333
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
3535 with the proposed code changes. Here are the command lines
3636 (substitute the user, branch, and fork names we found above):
3737
@@ -48,14 +48,14 @@ The instructions below are for command line use of git.
4848 ```
4949
5050
51- 4 . This has made a local branch named
51+ 3 . This has made a local branch named
5252 `contributorusername-contributor_branch_name`. Go ahead and test
5353 and review the PR and make code edits and new commits to your
5454 local branch as needed.
5555
5656
5757
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
5959 on Github from the fork), you will specify the upstream to be the
6060 contributor's fork:
6161
@@ -93,7 +93,7 @@ The instructions below are for command line use of git.
9393 ```
9494
9595
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
9797 the local branch (named
9898 `contributorusername-contributor_branch_name`).
9999
@@ -106,7 +106,7 @@ The instructions below are for command line use of git.
106106 *NOTE: If you encounter a permissions error, it is possible that the external
107107 contributor didn't grant access for collaboration on the branch.*
108108
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.
110110
111111
112112---
0 commit comments