人生不如意之事十之八九,合并分支往往也不是一帆風(fēng)順的。
準(zhǔn)備新的feature1分支,繼續(xù)我們的新分支開(kāi)發(fā):
$git checkout -b feature1Switchedto a new branch'feature1'
修改readme.txt最后一行,改為:
Creating anewbranch is quickANDsimple.
在feature1分支上提交:
$ git add readme.txt $ gitcommit-m"AND simple"[feature175a857c]ANDsimple1file changed,1insertion(+),1deletion(-)
切換到master分支:
$ git checkout masterSwitched to branch 'master'Your branch is ahead of 'origin/master' by 1commit.
Git還會(huì)自動(dòng)提示我們當(dāng)前master分支比遠(yuǎn)程的master分支要超前1個(gè)提交滩愁。
在master分支上把readme.txt文件的最后一行改為:
Creating anewbranch is quick & simple.
提交:
$git add readme.txt$git commit -m"& simple"[master400b400] & simple1file changed,1insertion(+),1deletion(-)
現(xiàn)在,master分支和feature1分支各自都分別有新的提交辫封,變成了這樣:
這種情況下硝枉,Git無(wú)法執(zhí)行“快速合并”,只能試圖把各自的修改合并起來(lái)倦微,但這種合并就可能會(huì)有沖突檀咙,我們?cè)囋嚳矗?/p>
$git merge feature1Auto-merging readme.txtCONFLICT(content):Mergeconflictinreadme.txtAutomaticmerge failed; fix conflictsandthencommit the result.
果然沖突了!Git告訴我們璃诀,readme.txt文件存在沖突弧可,必須手動(dòng)解決沖突后再提交。git status也可以告訴我們沖突的文件:
$git status# On branch master# Your branch is ahead of 'origin/master' by 2 commits.## Unmerged paths:#? (use "git add/rm ..." as appropriate to mark resolution)##? ? ? both modified:? ? ? readme.txt#no changes added to commit (use"git add"and/or"git commit -a")
我們可以直接查看readme.txt的內(nèi)容:
Git is a distributed version control system.Git is free software distributed under the GPL.Git has a mutable index called stage.Git tracks changes of files.<<<<<<>>>>>> feature1
Git用<<<<<<<劣欢,=======棕诵,>>>>>>>標(biāo)記出不同分支的內(nèi)容,我們修改如下后保存:
Creating anewbranch is quickandsimple.
再提交:
$git add readme.txt$git commit -m"conflict fixed"[master59bc1cb] conflict fixed
現(xiàn)在凿将,master分支和feature1分支變成了下圖所示:
用帶參數(shù)的git log也可以看到分支的合并情況:
$ git log --graph --pretty=oneline --abbrev-commit*59bc1cb conflict fixed|\| *75a857cANDsimple* |400b400 & simple|/* fec145a branch test...
最后校套,刪除feature1分支:
$git branch -d feature1Deletedbranch feature1 (was75a857c).
工作完成。
小結(jié)
當(dāng)Git無(wú)法自動(dòng)合并分支時(shí)牧抵,就必須首先解決沖突笛匙。解決沖突后侨把,再提交,合并完成妹孙。
用git log --graph命令可以看到分支合并圖秋柄。