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

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 Join to answer
Community showcase
Brian Ganninger
Published Jan 23, 2018 in Sourcetree

Tip from the team: workflow and keyboard shortcuts

Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...

525 views 0 4
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot