Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.45.1 → 2.47.0 no changes
-
2.45.0
04/29/24
- 2.43.1 → 2.44.2 no changes
-
2.43.0
11/20/23
- 2.41.1 → 2.42.3 no changes
-
2.41.0
06/01/23
- 2.38.3 → 2.40.3 no changes
-
2.38.2
12/11/22
- 2.38.1 no changes
-
2.38.0
10/02/22
- 2.37.1 → 2.37.7 no changes
-
2.37.0
06/27/22
- 2.31.1 → 2.36.6 no changes
-
2.31.0
03/15/21
- 2.22.1 → 2.30.9 no changes
-
2.22.0
06/07/19
- 2.20.1 → 2.21.4 no changes
-
2.20.0
12/09/18
- 2.12.5 → 2.19.6 no changes
-
2.11.4
09/22/17
- 2.2.3 → 2.10.5 no changes
-
2.1.4
12/17/14
-
2.0.5
12/17/14
DESCRIPTION
Use git mergetool to run one of several merge utilities to resolve
merge conflicts. It is typically run after git merge.
If one or more <file> parameters are given, the merge tool program will be run to resolve differences on each file (skipping those without conflicts). Specifying a directory will include all unresolved files in that path. If no <file> names are specified, git mergetool will run the merge tool program on every file with merge conflicts.
OPTIONS
- -t <tool>
- --tool=<tool>
-
Use the merge resolution program specified by <tool>. Valid values include emerge, gvimdiff, kdiff3, meld, vimdiff, and tortoisemerge. Run
git mergetool --tool-helpfor the list of valid <tool> settings.If a merge resolution program is not specified, git mergetool will use the configuration variable
merge.tool. If the configuration variablemerge.toolis not set, git mergetool will pick a suitable default.You can explicitly provide a full path to the tool by setting the configuration variable
mergetool.<tool>.path. For example, you can configure the absolute path to kdiff3 by settingmergetool.kdiff3.path. Otherwise, git mergetool assumes the tool is available in PATH.Instead of running one of the known merge tool programs, git mergetool can be customized to run an alternative program by specifying the command line to invoke in a configuration variable
mergetool.<tool>.cmd.When git mergetool is invoked with this tool (either through the
-tor--tooloption or themerge.toolconfiguration variable) the configured command line will be invoked with$BASEset to the name of a temporary file containing the common base for the merge, if available;$LOCALset to the name of a temporary file containing the contents of the file on the current branch;$REMOTEset to the name of a temporary file containing the contents of the file to be merged, and$MERGEDset to the name of the file to which the merge tool should write the result of the merge resolution.If the custom merge tool correctly indicates the success of a merge resolution with its exit code, then the configuration variable
mergetool.<tool>.trustExitCodecan be set totrue. Otherwise, git mergetool will prompt the user to indicate the success of the resolution after the custom tool has exited. - --tool-help
-
Print a list of merge tools that may be used with
--tool. - -y
- --no-prompt
-
Don’t prompt before each invocation of the merge resolution program.
- --prompt
-
Prompt before each invocation of the merge resolution program. This is the default behaviour; the option is provided to override any configuration settings.
TEMPORARY FILES
git mergetool creates *.orig backup files while resolving merges.
These are safe to remove once a file has been merged and its
git mergetool session has completed.
Setting the mergetool.keepBackup configuration variable to false
causes git mergetool to automatically remove the backup as files
are successfully merged.
GIT
Part of the git[1] suite
