Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why does SourceTree tell me no changes detected for unstaged files?

Anthony Gibbs April 9, 2025

SourceTree is correctly listing the files I've edited, but when I click on any of them, the internal diff area says "No changes in this file have been detected, or it is a binary file or it is configured to be ignored by the File patterns", and then opens a CodeCompare window which correctly displays the changes that were made.

Note my files are not binaries, and the File pattern settings are correct.

This started happening about two weeks ago. I have uninstalled, and then upgraded to latest version, with no change in behaviour; this makes SourceTree borderline unusable.

I have run

git config set diff.tool ''

in the hopes of stopping this, to no avail. Any ideas? 

3 answers

1 accepted

0 votes
Answer accepted
Ken Arromdee
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2025

It seems the problem can be fixed by going into options, git, uncheck "allow external diff drivers".  I can still do external diffs in other contexts.

Jeff Lett
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2025

Thanks for the suggestion, but I don't see that as an option.  Am I in the wrong place?Screenshot 2025-04-24 at 12.25.36 PM.png

Anthony Gibbs April 28, 2025

Brilliant, thanks @Ken Arromdee that did the trick :+1:

0 votes
Jeff Lett
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2025

Running into the same issue with a recent update.  Tried updating to 4.2.11 today and it still happens.  Probably going to try another client soon.

0 votes
Ken Arromdee
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 23, 2025

This has happened to me too.  I hadn't upgraded for a while and I upgraded and the problem immediately started happening.  There's obviously some kind of bug in the new version.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events