I have a project in a GIT repository which I manage through Source Tree. One file only has ceased to display a diff in the right hand pane even though it is shown as changed in the file/status tab and from the git command line. Instead the diff pane has the file name with a green icon with a tick in it. If I open the file and re-save it forcing UTF-8 (As there has been a reported bug about Unicode 16 files) with a text editor, the file is shown with a yellow icon with "Open before" and "Open after" buttons. I simply want source tree to display the diff information for this file again
The reason I was getting no diff in SourceTree (or in Terminal using `git diff`) was because the file in question was added as a Git LFS file.
Git (and SourceTree) do not seem to be able to diff text files added to LFS. However after a bit of hunting and I was able to fix this by running...
git config --global diff.lfs.textconv cat`
with help from the suggestion here...
(Note that adding and discard hunks in SourceTree is still broken even with this workaround)
Another explanation for why you might receive the message "No changes in this file have been detected, or it is a binary file" is because the file is a unicode or UTF-16 encoded file. Files with UTF-16 encoding are not recognized as text files by SourceTree (or specifically git diff). As a result you cannot view the file or compare changes.
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:
Create or modify the .gitattributes file in the root directory of the repository with the following line:
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.)
This is a link to www.stackoverflow.com's answers to this question: https://stackoverflow.com/questions/777949/can-i-make-git-recognize-a-utf-16-file-as-text
I encountered the same issue. SourceTree would not show up difference on the right pane. This just happens on specific file after we made some change to it.
It turned out that the file encoding was changed to UCS-2 Big Endian by mistake (previously UTF-8). Issue was resolved once we change it back to UTF-8.
SourceTree version 126.96.36.199509.
@Aaron Lavers Not much I can help you with there, I'm just another user. If the git diff had the same issue, I'd help you figure what was wrong with your files. However, since the SourceTree diff doesn't match the git diff, I recommend filing a bug report at jira.atlassian.com.
@Seth hey mate, when running through terminal the git process shows diffs as per usual, and in the Wakanda software I'm using it also displays the diffs correctly.
Part of me is wondering if that in itself is an issue - Wakanda performing it's own diffs, or even regenerating whole files (*though I'd still expect to just see one or two lines change).
It is unusual behaviour, though I am getting around it by viewing my diffs both on the github site as well as in the terminal.
Is there any sourcetree logs I can drag up to share that might help? I'm a bit of a noob with the gui sorry.
I have the same issue. Multiple lines edited on two files, file 1 highlights the first line (doctype declaration) in red as being deleted, the second file highlights all the changed lines as per normal.
Both files have had the same lines edited, yet one shows the diff, the other just displays like the attached screenshot.
This has been an issue for several weeks now.
Screen Shot 2016-01-27 at 2.52.16 pm.png
@Seth First I meant to say "sorry for posting to an old thread" too. I justified it by this just being a comment :) I did see the ellipses and even clicked on them. The only option given is to "Reverse File" which I know I didn't want, and there is no indication that the file is too large. I had a guess that might be it, and this post confirmed it. I'm not sure that this is worthy of a full-on feature request, but it would add some clarity for a known situation.
@Damon Overboe It kinda does - there is a ellipses (...) at the bottom of the diff. I won't try and argue that it is noticable, or even particularly meaningful, but it is something. You could file a feature request at jira.atlassian.com if you think it should be more explicit.
I experience the same issue. Just a single file in my repository, and other users of Source Tree also can not see the differences in the diff panel for the same file. I'm wondering if there is a size limitation of some kind. The file currently has 13,459 lines and 1,153,964 characters. Wildly inconvenient to not be able to see the change hunks, which means the features for only saving specific hunks do not work for this file either.
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
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