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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,112
Community Members
 
Community Events
176
Community Groups

SourceTree losing custom diff arguments

On 3.0.8, I have an external, custom diff tool defined with arguments.  I can set these via the options dialog, exit SourceTree, and can confirm they are stored in my .gitconfig file.  When I open SourceTree back up and go into the options, the arguments field (for both merge and diff tools) are blank.  The path to my custom command remains however.

Custom diff and merge command: C:\Program Files (x86)\WinMerge\WinMergeU.exe 
Diff arguments: -e -u -wl -dl \"Remote\" -dr "Local" $LOCAL $REMOTE
Merge arguments: -e -u -wl -dl \"Remote\" -dr "Local" $LOCAL $REMOTE $MERGED

 

I'm trying to call WinMerge in this way since the listed "WinMerge" entry in the dropdown

doesn't appear to work.  My custom configuration works great, it's just that the settings are being removed when the application is started - I can observe my settings being deleted from my .gitconfig on startup of the application.

 

 

2 answers

Seems to be STILL an issue and seriously affects using diff programs professionally from out of Sourcetree.

Oh, sorry, that seems to be wrong.  We had indeed command options being eaten on their way to our diff tool, but that just turned out not to be SourceTree's fault.

0 votes
minnsey Atlassian Team Nov 02, 2018

Hi,

I'm afraid this is a known bug, we are working on a fix.

And are you reserving the rest of the century to accomplish it?

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events