Documentation / config / merge.txton commit Merge branch 'jk/perf-lib-tee' (67e3ec1)
   1merge.conflictStyle::
   2        Specify the style in which conflicted hunks are written out to
   3        working tree files upon merge.  The default is "merge", which
   4        shows a `<<<<<<<` conflict marker, changes made by one side,
   5        a `=======` marker, changes made by the other side, and then
   6        a `>>>>>>>` marker.  An alternate style, "diff3", adds a `|||||||`
   7        marker and the original text before the `=======` marker.
   8
   9merge.defaultToUpstream::
  10        If merge is called without any commit argument, merge the upstream
  11        branches configured for the current branch by using their last
  12        observed values stored in their remote-tracking branches.
  13        The values of the `branch.<current branch>.merge` that name the
  14        branches at the remote named by `branch.<current branch>.remote`
  15        are consulted, and then they are mapped via `remote.<remote>.fetch`
  16        to their corresponding remote-tracking branches, and the tips of
  17        these tracking branches are merged.
  18
  19merge.ff::
  20        By default, Git does not create an extra merge commit when merging
  21        a commit that is a descendant of the current commit. Instead, the
  22        tip of the current branch is fast-forwarded. When set to `false`,
  23        this variable tells Git to create an extra merge commit in such
  24        a case (equivalent to giving the `--no-ff` option from the command
  25        line). When set to `only`, only such fast-forward merges are
  26        allowed (equivalent to giving the `--ff-only` option from the
  27        command line).
  28
  29merge.verifySignatures::
  30        If true, this is equivalent to the --verify-signatures command
  31        line option. See linkgit:git-merge[1] for details.
  32
  33include::fmt-merge-msg.txt[]
  34
  35merge.renameLimit::
  36        The number of files to consider when performing rename detection
  37        during a merge; if not specified, defaults to the value of
  38        diff.renameLimit. This setting has no effect if rename detection
  39        is turned off.
  40
  41merge.renames::
  42        Whether and how Git detects renames.  If set to "false",
  43        rename detection is disabled. If set to "true", basic rename
  44        detection is enabled.  Defaults to the value of diff.renames.
  45
  46merge.renormalize::
  47        Tell Git that canonical representation of files in the
  48        repository has changed over time (e.g. earlier commits record
  49        text files with CRLF line endings, but recent ones use LF line
  50        endings).  In such a repository, Git can convert the data
  51        recorded in commits to a canonical form before performing a
  52        merge to reduce unnecessary conflicts.  For more information,
  53        see section "Merging branches with differing checkin/checkout
  54        attributes" in linkgit:gitattributes[5].
  55
  56merge.stat::
  57        Whether to print the diffstat between ORIG_HEAD and the merge result
  58        at the end of the merge.  True by default.
  59
  60merge.tool::
  61        Controls which merge tool is used by linkgit:git-mergetool[1].
  62        The list below shows the valid built-in values.
  63        Any other value is treated as a custom merge tool and requires
  64        that a corresponding mergetool.<tool>.cmd variable is defined.
  65
  66merge.guitool::
  67        Controls which merge tool is used by linkgit:git-mergetool[1] when the
  68        -g/--gui flag is specified. The list below shows the valid built-in values.
  69        Any other value is treated as a custom merge tool and requires that a
  70        corresponding mergetool.<guitool>.cmd variable is defined.
  71
  72include::../mergetools-merge.txt[]
  73
  74merge.verbosity::
  75        Controls the amount of output shown by the recursive merge
  76        strategy.  Level 0 outputs nothing except a final error
  77        message if conflicts were detected. Level 1 outputs only
  78        conflicts, 2 outputs conflicts and file changes.  Level 5 and
  79        above outputs debugging information.  The default is level 2.
  80        Can be overridden by the `GIT_MERGE_VERBOSITY` environment variable.
  81
  82merge.<driver>.name::
  83        Defines a human-readable name for a custom low-level
  84        merge driver.  See linkgit:gitattributes[5] for details.
  85
  86merge.<driver>.driver::
  87        Defines the command that implements a custom low-level
  88        merge driver.  See linkgit:gitattributes[5] for details.
  89
  90merge.<driver>.recursive::
  91        Names a low-level merge driver to be used when
  92        performing an internal merge between common ancestors.
  93        See linkgit:gitattributes[5] for details.