For instance, after clicking on HEAD, I see
Displaying all changes between 19e9eb6b0c81aaa80227a15357d2b9e5ba3053cc and working copy
Since that 19e9 is ancient, this diff takes ages. The only way I have found to "fix" this is to close SourceTree and reopen it. Is this a feature of sourcetree I am somehow triggering and how do I turn it off when I enable it?
If this is a bug, is it a known one that will be fixed soon? when it happens, it pretty much mandates closing SourceTree as every operation takes minutes to complete.
Note, this isn't when using shift to select multiple items. This is single clicking without modifiers pressed. Though a modifier key might have been pressed earlier but isn't anymore. Pressing and releasing mod keys (alt/ctrl/shift) does not fix it.
Definitely a UI bug, I get this all the time. When "Displaying all changes between xxx and yyy" appears, SourceTree thinks you have two commits selected, but you have only one.
This occurs when the commit window refreshes while you're working, so your selected commit disappears. Internally, SourceTree thinks it's still selected, but you can't de-select it through normal actions, e.g. selecting another commit.
Workaround: Hit Ctrl-A to select all commits in the window. Then click on a commit. It should show normally again.
Hi Brian, this actually sounds like it could be a bug. Please provide some more information so we can reproduce it:
Beyond Compare for Diff
Windows 10 OS
The commit isn't always the same one. But certain commits seem to come up often.
When I notice it broken is often shortly after having tabbed back into the program. So it could be an issue with what's done when SourceTree is not in focus.
IE, work in Visual Studio. Tab to SourceTree to check diffs/commit working change/etc. Suddenly diff window has one item highlighted but the diff is across a large number and takes forever to generate/refresh.
It seems if I check/uncheck the show all branches it will fix the problem without restarting.
Same here Windows 10 with SourceTree 22.214.171.124.
Note this usually happens when there are uncommitted and unstaged changed files. When I commit these file the issue is gone for a time. But it comes back often (probably after some commit or branch checkout, but I can't tell for sure what the actual reason is).
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
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