Launch External Merge Tool For Sourcetree Mac

In most cases of merge conflicts, users are stuck with auto-merge or manually resolving it by hand. This is because in the free version of GitKraken, users have limited options to choose from (keep file, auto-merge, or use external merge tool). We’re thrilled to introduce the latest addition to the Atlassian distributed version control system (DVCS) family – Sourcetree for Windows. Sourcetree is a free Git desktop client for developers on Windows.Say goodbye to the command line and use the full capabilities of Git through Sourcetree’s beautifully simple interface (and stop being jealous of what your Mac friends are using).

Sourcetree Mac Download

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sourcetree merge conflict tool

Comments

commented Jun 25, 2017

For

Sublime Text version number: Dev channel, Build 3139

Git version number: 2.13.0 (Apple Git-88)

OS type and version: macOS Sierra, 10.12.5

Console error output:

A description of the problem:
On attempting to launch an external merge tool to resolve a conflict, nothing happens.
Inspecting the console shows this -

Relevant section of my gitconfig file:

Output of git config merge.tool is diffmerge.

Output of git config mergetool.diffmerge.cmd is - diffmerge --merge --result='$MERGED' '$LOCAL' '$BASE' '$REMOTE'

Steps to reproduce, if possible: I'm not entirely sure, I switched back to using my older Mac after encountering this issue on my current one. Very similar setup with just a difference in hardware (2015 vs 2013).

added the not-enough-information label Jun 25, 2017

commented Jun 25, 2017

Hi @oddysee , thank you for reporting the issue! Kindly help us with a few more details:

  • Output of git config -l | grep merge

  • Result of running git mergetool on it's own in a shell

  • If the above still doesn't provide enough information, please record and attach a debug log like so:

    1. Open sublime, and get to the state of conflict just prior to running the merge command
    2. Open command palette, and run the command 'GitSavvy: enable logging'
    3. Perform the failing 'Launch external merge tool' command.
    4. Run the command 'GitSavvy: disable logging'
    5. Run the command 'GitSavvy: view recorded log', save the file and attach it here. Take care to remove any sensitive information that may be recorded in GitSavvy.

commented Aug 2, 2017
edited

Best

I am seeing the same issue on one of my machines but not another. I do have a different mergetool than the OP. Here is the info you asked for:

  • **Output of git config -l | grep merge:
  • Result of git mergetool: Mergetool correctly opens up and works as expected.
  • Result of GitSavvy debug log attached. gitsavvy-log.txt

As noted, running git mergetool works just fine, so it's not a major issue; but I can't figure out why one of my machines works and another doesn't when I hit M from the status screen to run the mergetool. Both machines have the same config. Any help would be appreciated.

Thank you for all your work on GitSaavy... it's a great tool that I use every day and sure appreciate it!!

commented Aug 12, 2017
edited

Result of GitSavvy debug log attached.

Where is it?

commented Aug 12, 2017

Where is it?

Sorry, not sure what happened. I updated the comment with the attached log.

commented Aug 20, 2017

@theiviaxx
Can you inspect the console and see if it prints an error? maybe there is a problem with the path

added a commit to asfaltboy/GitSavvy that referenced this issue Aug 22, 2017
Other: refactor log_git and add log_process

Launch External Merge Tool For Sourcetree Mac Documentation

commented Aug 22, 2017

@thezimmee are you sure that the issue occurred in the attached log? There doesn't seem that there is --verbose anywhere in the merge command to be executed.

If you still have the issue, I have created a branch that adds a bit more logging about executed command over here: feature/add-process-debug-log

Please try it out and add the new output here.

commented Aug 22, 2017

@asfaltboy OP here, I discovered that a botched install of a Git client (SourceTree) had mangled the gitconfig, which was resulting in the --verbose merge tool command.

Apologies for the confusion and thanks for all the assistance. Leaving this open for @thezimmee, though I'd suggest his issue is different and he'd be better off opening a separate issue.

Merged
added a commit to asfaltboy/GitSavvy that referenced this issue Aug 22, 2017
Other: refactor log_git and add log_process
added a commit to asfaltboy/GitSavvy that referenced this issue Aug 22, 2017
Other: refactor log_git and add log_process

commented Aug 22, 2017

I recently installed the dev build of Sublime, and for whatever reason that seemed to resolve the issue for me. Thanks for your help guys, I will let you know if I see it again.

Sourcetree Merge Conflicts

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment