Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[testcase notes] #29: Git merge categorization #75

Open
dorawyy opened this issue Nov 13, 2017 · 2 comments
Open

[testcase notes] #29: Git merge categorization #75

dorawyy opened this issue Nov 13, 2017 · 2 comments

Comments

@dorawyy
Copy link
Owner

dorawyy commented Nov 13, 2017

git merge Categorization

Intro of different options --> #64

Fast-forward Merge

fast-forward-merge

Three-way Merge

three-way-merge

@dorawyy
Copy link
Owner Author

dorawyy commented Nov 13, 2017

Three-way Merge

Three-way merge with single conflict

git checkout mt3
git merge mt4

1

git checkout mt3
git merge mt4 --no-commit

2

git checkout mt3
git merge mt4 --squash

3

Additional test: if commit6 created a new file, not existing in mt3 after commit5:

4

@dorawyy
Copy link
Owner Author

dorawyy commented Nov 13, 2017

Three-way merge with no conflict

git checkout mt1
git merge mt2 

wechatimg325

git checkout mt1
git merge mt2 --no-commit

wechatimg326

git checkout mt1
git merge mt2 --squash

wechatimg327

Additional test: If commit6 happens after commit5, then merge; No matter what merge option (normal/squash/no-commit) file in commit6 will always be seen bymt1.

wechatimg328

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant