Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


External diff tools not launching - gitconfig not edited




I have SourceTree version 3.3.8 for Windows.

I read about using BeyondCompare as a diff and a merge tool, and how to set them up. I am afraid it doesn't work and solutions offered in the past here and in StackOverflow do not work.

Here is how my Tools->Options->General tab is set up:SourceTree_XylccIUv08.png


Here is how the ools->Options->Diff tab is set up:


However, my gitconfig file remains:

tool = KDiff3
guitool = KDiff3

Is this a bug, is there anything else I forgot to configure?


1 answer

1 vote
Deleted user Apr 07, 2020


I have the exact same problem on one computer - having another one working perfectly.
I tried many, many things - I was not able to fix it and it is driving me crazy - slowly convinced to go away from SourceTree... :-(

On one computer the diff is working perfectly, on the other it does not open the diff.
I noticed that on the non working computer, the global gitconfig is not written when pressing OK in the Options dialog (it is written properly on the working computer).

Looking more closely to the non working computer (see below), I can see that there is a problem accessing that file. Any idea on what could be wrong ? I have access rights to that folder.

Any hints will be appreciated.


Did you find an answer to this? We're running into this exact problem with only certain people's machines, and your debugging appears to be getting close to root of the problem. 


Thank you!


No, I didn't find an answer and no one from Atlassian contacted me privately. I just avoided using this feature.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events