Git status during merge conflict

From genomewiki
Revision as of 01:11, 31 August 2016 by Galt (talk | contribs) (Created page with " Running git status during a merge-conflict can often show a scarily-large number of files. These represent the work of other people in the group. If it has been several days sin...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Running git status during a merge-conflict can often show a scarily-large number of files. These represent the work of other people in the group. If it has been several days since your last pull, there could be dozens and dozens of files that were changed by other people.

This is in fact perfectly normal for merge-commits. There is no need to worry. Just resolve the conflicts listed under git status with the editor, looking for git conflict markers. After resolving the conflict, do git add for each file. When all have been resolved, do

git commit -m 'fixed merge conflict.'