I'm using the File Log View and Blame to trace a change in the code. At one point, the file is renamed, so only appears in the File Log View if Follow Renames is checked. After checking Follow Renames and finding the next earlier revision to Blame, I select Blame Selected, but an error dialog appears with:

Error encountered

'git blame' failed with code 128:'fatal: no such path new/path/filename.py in abcdef'

Where new/path/filename.py is the current name of the file but at this revision, the filename is old/path/filename.py.

It would be nice if, since sourcetree is following the renamed files if it would use the old name, because the blame will never work for the target hash with the new name.