alvaro/git-flight-rules
1
0
Fork 0
mirror of https://github.com/k88hudson/git-flight-rules.git synced 2025-03-10 12:48:43 -03:00
Code Issues Releases Wiki Activity

Added then

Browse Source 
This makes it clear that `git rebase` is not a check to see if master is up to date. #3
This commit is contained in:
Richard Littauer 2015-03-14 11:06:23 -07:00
parent a2d407f12e
commit 19c8ad3ab9
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -42,7 +42,7 @@ In general, **avoid force pushing**. It is best to create and push a new commit
You need to do something called an interactive rebase.
If you are working in a branch that is/will become a pull-request against `master`, you can rebase against your `master` branch. Make sure it is up to date:
If you are working in a branch that is/will become a pull-request against `master`, you can rebase against your `master` branch. Make sure the master branch is up to date, then:
```
(my-branch)$ git rebase -i master