Blame in SourceTree for Windows


I have a problem with SourceTree for Windows:

When I use the command "Blame selected", all lines are in the state "Not committed yet" and no changes are shown.

I found out that the standard blame command blames the file in the working copy and as the setting "autocrlf" is "true", all lines are considered to be changed there.

Is there a possibility to change the behaviour of the git blame function to blame the currently selected branch?


1 answer

1 accepted

Accepted Answer
1 vote

I've created a feature request for this:

If your file is showing as completely modified, and you already have autocrlf=true, then it means it was committed from a machine with an incorrect setting. You will want to normalise the line endings and re-commit it to stop it permanently showing as modified in future.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published May 30, 2018 in Sourcetree

Tip from the team: configuring Git or Mercurial in Sourcetree

Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...

992 views 2 3
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you