]>
Commit | Line | Data |
---|---|---|
ea24a76a NTND |
1 | mergetool.<tool>.path:: |
2 | Override the path for the given tool. This is useful in case | |
3 | your tool is not in the PATH. | |
4 | ||
5 | mergetool.<tool>.cmd:: | |
6 | Specify the command to invoke the specified merge tool. The | |
7 | specified command is evaluated in shell with the following | |
8 | variables available: 'BASE' is the name of a temporary file | |
9 | containing the common base of the files to be merged, if available; | |
10 | 'LOCAL' is the name of a temporary file containing the contents of | |
11 | the file on the current branch; 'REMOTE' is the name of a temporary | |
12 | file containing the contents of the file from the branch being | |
13 | merged; 'MERGED' contains the name of the file to which the merge | |
14 | tool should write the results of a successful merge. | |
15 | ||
9d9cf230 SH |
16 | mergetool.<tool>.hideResolved:: |
17 | Allows the user to override the global `mergetool.hideResolved` value | |
18 | for a specific tool. See `mergetool.hideResolved` for the full | |
19 | description. | |
20 | ||
ea24a76a NTND |
21 | mergetool.<tool>.trustExitCode:: |
22 | For a custom merge command, specify whether the exit code of | |
23 | the merge command can be used to determine whether the merge was | |
24 | successful. If this is not set to true then the merge target file | |
4d542687 EN |
25 | timestamp is checked, and the merge is assumed to have been successful |
26 | if the file has been updated; otherwise, the user is prompted to | |
ea24a76a NTND |
27 | indicate the success of the merge. |
28 | ||
29 | mergetool.meld.hasOutput:: | |
30 | Older versions of `meld` do not support the `--output` option. | |
31 | Git will attempt to detect whether `meld` supports `--output` | |
32 | by inspecting the output of `meld --help`. Configuring | |
33 | `mergetool.meld.hasOutput` will make Git skip these checks and | |
34 | use the configured value instead. Setting `mergetool.meld.hasOutput` | |
35 | to `true` tells Git to unconditionally use the `--output` option, | |
36 | and `false` avoids using `--output`. | |
37 | ||
dbd8c09b LS |
38 | mergetool.meld.useAutoMerge:: |
39 | When the `--auto-merge` is given, meld will merge all non-conflicting | |
4d542687 | 40 | parts automatically, highlight the conflicting parts, and wait for |
dbd8c09b LS |
41 | user decision. Setting `mergetool.meld.useAutoMerge` to `true` tells |
42 | Git to unconditionally use the `--auto-merge` option with `meld`. | |
43 | Setting this value to `auto` makes git detect whether `--auto-merge` | |
44 | is supported and will only use `--auto-merge` when available. A | |
45 | value of `false` avoids using `--auto-merge` altogether, and is the | |
46 | default value. | |
47 | ||
7b5cf8be FR |
48 | mergetool.vimdiff.layout:: |
49 | The vimdiff backend uses this variable to control how its split | |
cf6cac20 | 50 | windows appear. Applies even if you are using Neovim (`nvim`) or |
7b5cf8be FR |
51 | gVim (`gvim`) as the merge tool. See BACKEND SPECIFIC HINTS section |
52 | ifndef::git-mergetool[] | |
53 | in linkgit:git-mergetool[1]. | |
54 | endif::[] | |
55 | for details. | |
56 | ||
98ea309b | 57 | mergetool.hideResolved:: |
4d542687 | 58 | During a merge, Git will automatically resolve as many conflicts as |
98ea309b SH |
59 | possible and write the 'MERGED' file containing conflict markers around |
60 | any conflicts that it cannot resolve; 'LOCAL' and 'REMOTE' normally | |
61 | represent the versions of the file from before Git's conflict | |
edbf9a2e | 62 | resolution. This flag causes 'LOCAL' and 'REMOTE' to be overwritten so |
98ea309b SH |
63 | that only the unresolved conflicts are presented to the merge tool. Can |
64 | be configured per-tool via the `mergetool.<tool>.hideResolved` | |
b2a51c1b | 65 | configuration variable. Defaults to `false`. |
98ea309b | 66 | |
ea24a76a NTND |
67 | mergetool.keepBackup:: |
68 | After performing a merge, the original file with conflict markers | |
69 | can be saved as a file with a `.orig` extension. If this variable | |
70 | is set to `false` then this file is not preserved. Defaults to | |
71 | `true` (i.e. keep the backup files). | |
72 | ||
73 | mergetool.keepTemporaries:: | |
74 | When invoking a custom merge tool, Git uses a set of temporary | |
75 | files to pass to the tool. If the tool returns an error and this | |
76 | variable is set to `true`, then these temporary files will be | |
4d542687 | 77 | preserved; otherwise, they will be removed after the tool has |
ea24a76a NTND |
78 | exited. Defaults to `false`. |
79 | ||
80 | mergetool.writeToTemp:: | |
81 | Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of | |
82 | conflicting files in the worktree by default. Git will attempt | |
83 | to use a temporary directory for these files when set `true`. | |
84 | Defaults to `false`. | |
85 | ||
86 | mergetool.prompt:: | |
87 | Prompt before each invocation of the merge resolution program. | |
42943b95 TK |
88 | |
89 | mergetool.guiDefault:: | |
90 | Set `true` to use the `merge.guitool` by default (equivalent to | |
91 | specifying the `--gui` argument), or `auto` to select `merge.guitool` | |
92 | or `merge.tool` depending on the presence of a `DISPLAY` environment | |
93 | variable value. The default is `false`, where the `--gui` argument | |
94 | must be provided explicitly for the `merge.guitool` to be used. |