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

I can't see the diff. It incorrectly says "No changes in this file have been detected"


5 answers

7 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 29, 2017

Have you tried increasing the size of the files supported in the Diff settings tab? It may be too large for preview based on the defaults.

This worked for me, thanks!!!

Deleted user Nov 23, 2018

Thanks, worked for me as well!

thanks. it works.


I get buggy behavior in SourceTree. When I compare two branches, it 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

None of the conditions listed in the error message are true for my file. There are changes. It is a text file. The file is not ignored.

There are just 1821 lines in my file. 🐞🐞🐞 

Aside from the size limit another reason for this message is that the file is encoded with UTF-16.  Atlassian SourceTree does not properly recognize unicode and UTF-16 files as text which makes them unviewable and uncomparable under SourceTree (specifically git diff).

If the file suffix of the UTF-16 files is known (*.uni for example) then all files with that suffix can be associated with UTF-16 to UTF-8 converter with the following two changes:

  1. Create or modify the .gitattributes file in the root directory of the repository with the following line:

     *.uni diff=utf16
  2. Then modify the .gitconfig file in the users home directory (C:\Users\yourusername\.gitconfig) with the following section:

        textconv = "iconv -f utf-16 -t utf-8"

These two changes should take effect immediately without reloading the repository into SourceTree. It applies the text conversion to all *.uni files which makes them viewable and comparable like other text files. If other files need this conversion you can add additional lines to the .gitattributes file. (If the designated file(s) are NOT UTF-16 you will get unreadable results for that file.)

The conversion process is invisible and does not affect or touch the file itself.

It works. thanks.

The size limit in the diff tab fixed it for me also. This is really invisible. Please show this is the issue in the UI when the diff does not show since it just looks like it is treating it as Binary at the moment.

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 29, 2017


Ultimately Sourcetree relies on the 'git diff' command for that information. Typically you will see that if the file is binary or encoded as something other than ASCII.

You can see what git thinks the diff is by opening the Terminal and running git diff against that file. See

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events