Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b9cc78e

Browse files
committed
Correct git command for deleting a local branch
1 parent b1bed41 commit b9cc78e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -32,14 +32,14 @@ To reiterate this repository is to get people (you!) comfortable with using GitH
3232
* `git commit -m "More formal greeting"`
3333
* Do another `git push origin <branch>` and changes show automatically show up in the PR (No need to open another PR).
3434

35-
#### Maintaining your Fork Up-to-Date with the Project Branch
35+
#### Maintaining Your Fork Up-to-Date with the Project Branch
3636
After your commit has been merged, you may want to maintain your local fork up to date:
3737

3838
* 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`
3939
* Fetch the master branch from upstream `git fetch upstream`
4040
* Checkout your fork's local master branch `git checkout master`
4141
* 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`
4343
* To ensure that your fork on GitHub is also up-to-date you can do `git push origin master`
4444

4545
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

Comments
 (0)