Fixed in Sourcetree 4.2.1

Hi 5f59edad09de We understand the concerns and are working towards releasing the version 4.2.1.

Seriously, can we get version 4.2.1 with the fix before Christmas?
I can't believe you guys act so indifferently and inefficiently against an issue which has a such huge negative impact on user experience.

We have started working on this issue and would like to mention that the fix will be available on version 4.2.1.

The issue happens in every repo.

Example: https://github.com/facebook/jest

What are the chances that this may already be an editable property in some configuration file in the bundle? Has anyone looked?

If you give us access to the repo, one of us (commenters) will gladly fix the bug for you.

Hey, thank you for the app I enjoy working with for so many years, but this bug is still there in 4.1.9 (245) on mac and it is really ruining one of the main features – checking the diffs – to the point app is unusable because guessing on the lines slowing the whole process a lot. Please consider reprioritizing this bug.

Editing or reviewing changes in source files after looking at a diff is an incredibly common thing to do, but you need to know the line number in the modified source file in order to find the change.

This should marked high priority, not low!

Dear SourceTree dev team, this issue is super annoyingly sits there for years already and forces to spend nerve cells and dev time for guessing lines. All macs are affected! This is likely an easy to fix thing. It has to become a priority please!!