How to get 3-way merge in GIT on non-conflict merges?

Question

How to disable auto-merging in GIT?

The purpose is to have the same behaviour as for conflict merges resolution in automatic merges during invocatio

Answer 1

The trick is, the way git solves merges is:

• always based on a 3-way merges (since the graph of commits allows to get a common ancestor very easily)
• always seamlessly except for conflict (where the process gets assisted by you)

So even if you define a merge driver, it won't kick in unless there is a conflict of some sort.

---

The first setting to try is to define a merge attribute Unset

Unset

Take the version from the current branch as the tentative merge result, and declare that the merge has conflicts. This is suitable for binary files that does not have a well-defined merge semantics.

You would write in a .gitattributes file

 * -merge

, and see if that is enough to trigger the mergetool on all merged files.

---

One reason this "unset" feature is not directly an option of git merge, is that:

• merge is the main feature of a DVCS
• merge is done at the tree level (considering the all project)

Trying to unset the 3-way merge at the file level is not part of that merge process (which, again, reason at the tree level).
So it is more suited as an attribute which can be set for a specific set of files.

Answer 2

For changes that were made only on one side or the other, you can prevent automatic merges by unsetting the merge attribute (see gitattributes under “Performing a three-way merge”). A merge made for a pathname that lacks the merge attribute (or has it set to “binary”) will leave the version from the current branch in the working tree and leave the index entry for the pathname in a conflicted state.

If you want to encourage everyone to work this way, you can put in into a .gitattributes file and commit it. If you only want to do this for yourself, you can put it in an uncommited .gitattributes files or put it in your repository's $GIT_DIR/info/attributes file (which you could add/remove/rename at will to enable/disable the attribute).

#    repository/.git/info/attributes
# OR
#    .gitattributes
* -merge

If an identical change is made on both sides, even this configuration will not cause a conflict.