Skip to content

Commit

Permalink
Merge pull request #102 from Dheyson/patch-1
Browse files Browse the repository at this point in the history
Update git-en.md
  • Loading branch information
timeTravelCYN committed Aug 7, 2018
2 parents ebd8d29 + 35711b7 commit 1430469
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Git/git-en.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

This is not for rookie, we'll introduce somthing about more advanced.
This is not for rookie, we'll introduce something about more advanced.
## Merge with Rebase
This command shows no difference with the command `merge`.

Expand All @@ -21,7 +21,7 @@ After using `rebase ` , the commits from `develop` will be moved to the third `c

![](https://user-gold-cdn.xitu.io/2018/4/23/162f11cc2cb8b332?w=505&h=563&f=png&s=26514)

Compare with `merge`, the result of `rebase` is very clear with a single flow. But if there is any conflict, you'll be in troule to solving them. You have to solve them one by one , while you only need to solve them one-time if using `merge`.
Compare with `merge`, the result of `rebase` is very clear with a single flow. But if there is any conflict, you'll be in trouble to solving them. You have to solve them one by one , while you only need to solve them one-time if using `merge`.

You should use `rebase` on the local branchs which need be rebased. If you need to `rebase` the `develop` to the `master`, you should do as follows:

Expand Down

0 comments on commit 1430469

Please sign in to comment.