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

Update README.md

Browse Source
This commit is contained in:
Cameron Drake 2014-07-29 11:53:00 -07:00
parent 69204cdf0a
commit 978e484967
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -109,6 +109,15 @@ If everything is successful, you should see something like this:
``` ```
(master)$ Successfully rebased and updated refs/heads/master. (master)$ Successfully rebased and updated refs/heads/master.
``` ```
### Possible issues with merging
Safe merging strategy:
```sh
(master)$ git merge --no-ff --no-commit featurebranch
```
#### I need to merge a branch into a single commit
```sh
(master)$ git merge --squash featurebranch
```
### Possible issues with interactive rebases ### Possible issues with interactive rebases
@ -153,6 +162,11 @@ some code
You will need to resolve the differences between the code that was added in your new commit (in the example, everything from the middle line to `new-commit`) and your `HEAD`. You will need to resolve the differences between the code that was added in your new commit (in the example, everything from the middle line to `new-commit`) and your `HEAD`.
Sometimes these merges are complicated and you should use a visual diff editor:
```sh
(master*)$ git mergetool -t opendiff
```
After you have resolved all conflicts and tested your code, `git add` the files you have changed, and then continue the rebase with `git rebase --continue` After you have resolved all conflicts and tested your code, `git add` the files you have changed, and then continue the rebase with `git rebase --continue`
``` ```
@ -267,4 +281,3 @@ And finally, let's cherry-pick the commit for bug #14:
``` ```
(14)$ git cherry-pick 5ea5173 (14)$ git cherry-pick 5ea5173
``` ```