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!


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
Community Members
Community Events
Community Groups

Sourcetree and Beyond Compare Diff/Merge reset all the time

The Beyond Compare executable always changes back to the incorrect one causing the diff to fail on more than one file.

Sourcetree does not appear to save the path correctly and I have to modify it almost every time I relaunch it.

Sourcetree should use BComp.exe and not BCompare.exe for the Diff. This is the same as the Merge tool, which does appear to work properly.

2 answers

1 accepted

0 votes
Answer accepted

Update to SourceTree 3.1.1

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 23, 2019 • edited


Can you check you are running v3.0.15 this loss of settings should be fixed in that release.

We are looking into the use of BComp.exe vs BCompae.exe as it appears to work correctly for us and looking at other than opening an instance per comparison vs opening a tab per comparison they don't appear to operate differently. However if you have additional information  please let us know.

BComp must be used or every secondary diff will only load the right pane and not the left. I updated to 3.0.15 and this issue is still present.


I was told to use BComp.exe and not BCompare.exe by the folks at Beyond Compare.

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 30, 2019

Thanks for the information

Additionally, closing SourceTree and reopening it returns the Beyond Compare diff settings back to BCompare.exe (my original problem reported here).

I believe it relates to the way BCompare.exe only opens one window and BComp.exe pushes to the same open window:

Looks like this is now fixed in 3.1.1 (per release notes and testing)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events