You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -32,14 +32,14 @@ To reiterate this repository is to get people (you!) comfortable with using GitH
32
32
*`git commit -m "More formal greeting"`
33
33
* Do another `git push origin <branch>` and changes show automatically show up in the PR (No need to open another PR).
34
34
35
-
#### Maintaining your Fork Up-to-Date with the Project Branch
35
+
#### Maintaining Your Fork Up-to-Date with the Project Branch
36
36
After your commit has been merged, you may want to maintain your local fork up to date:
37
37
38
38
* Add the project branch as an [upstream repository](https://help.github.com/articles/configuring-a-remote-for-a-fork/) i.e. `git remote add upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git`
39
39
* Fetch the master branch from upstream `git fetch upstream`
40
40
* Checkout your fork's local master branch `git checkout master`
41
41
* Merge the upstream/master `git merge upstream/master`
42
-
* At this point you can always delete your local branch that you created (if you no longer need it) i.e. `git delete -b training-branch`
42
+
* At this point you can always delete your local branch that you created (if you no longer need it) i.e. `git branch -d training-branch`
43
43
* To ensure that your fork on GitHub is also up-to-date you can do `git push origin master`
44
44
45
45
This only scratches the surface of what is possible with git and GitHub. Feel free continue to use this repo when you need to test out (or document for others!) more complicated workflow.
0 commit comments