Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

Untitled.png

4 answers

5 votes
bgannin Atlassian Team 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!

0 votes
minnsey Atlassian Team Dec 29, 2017

Hi

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 https://git-scm.com/docs/git-diff

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.

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:

    [diff=utf16]
        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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,289 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you