Skip to content

Commit dab1cd8

Browse files
committed
Changed order and minor fixes
1 parent 437df67 commit dab1cd8

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

_docs/developer/getting_started/commit_to_PR_from_fork.md

+9-8
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,15 @@ The instructions below are for command line use of git.
4040
```
4141
4242
Additionally, find the name of the fork on the fork's page on Github.
43-
The `fork_name` may simply be `Submitty`, or the author may have chosen to another name.
43+
The `fork_name` may simply be `Submitty`, or the author may have chosen another name.
44+
45+
Note: make sure your git credentials are set before pulling or pushing to a forked
46+
repo. You can do this with the following commands. Use the `--global` flag if you
47+
want to set this outside of just Submitty.
48+
```
49+
git config user.name "Your Name"
50+
git config user.email "Your Email"
51+
```
4452
4553
4654
3. Next, make a local branch on your computer in your working repository
@@ -65,13 +73,6 @@ The instructions below are for command line use of git.
6573
and review the PR and make code edits and new commits to your
6674
local branch as needed.
6775
68-
Note: make sure your git credentials are set before pulling or pushing to a forked
69-
branch. You can do this with the following commands. Use the --global flag if you
70-
want to set this outside of just Submitty.
71-
'''
72-
git config user.name "Your Name"
73-
git config user.email "Your Email"
74-
'''
7576
7677
7778
5. In order to push the changes to the contributor's fork (and the PR

0 commit comments

Comments
 (0)