[Feature Request] Show relevent tag in line blame

[tecosaur]

I'll keep this short and sweet.

It would be nice if the Line Blanes could be configured to show the relevant tag for the commit, for instance - in what release the commit was first included in.

thanks,

tecosaur

[eamodio]

@tecosaur where would you like to see this? Can you send a screenshot of where?

[tecosaur]

Does this work as an example?

Addendum: To clarify, the v6.0.0 tag was not applied to this commit, however, it was the first tag after this commit was made, i.e. the version which the commit was shipped in.

[eamodio]

@tecosaur do you know the git command that would provide this information?

[tecosaur]

This could do the trick

git describe --contains ${"$(git blame -l -L ${lineno},${lineno} ${filename})"/%\ */} | cut -d'~' -f1

Without using bash it should be possible to do this with a few more steps

• git blame -l -L ${lineno},${lineno} ${filename}
• get hash part of output (first word)
• run git describe --contains ${hashOutputFromBlame}
• Remove the ...~XYZ bit from end of output
• you're left with the nearest tag

This should work for any annotated tag.

[tecosaur]

@eamodio any chance of an update?

[eamodio]

@tecosaur I would definitely welcome a PR for this, but this is not currently on my priority list

[tecosaur]

@eamodio would you be willing to point me to the relevant bits of the codebase?

[eamodio]

@tecosaur Can you explain more about this feature and why it is valuable? I think this change will be a bit involved (since it touches a bunch of different pieces) and the line blame is performance sensitive so it needs to do as little as possible as quickly as possible (granted if it is fully opt-in then that can change some).

[tecosaur]

Sure 😃

Use Case

To outline the use case for it I'll give two examples of where I'd find this useful. Hopefully, that would be sufficient.

Notes

I'm a uni student, and I take my notes digitally in LaTeX. At the end of each week, I add a tag for that week.
I often want to see when a specific bit of information was given etc. At the moment the process I follow is something like this

1. Look at commit message from the gitlense blame
2. Open up git history with Git Graph
3. Scroll and search for commit
4. See which is the next tag

What it could be is

1. Look at 'next tag' in Gitlense blame

A vscode extension

Someone reports a bug that started with the current version. There are a lot of commits going on, from different authors. I look at the relevant lines for the feature in question. I wonder if a specific line could be the cause. Here it would be very helpful if I could see at a glance what release that line was last updated in.

Performance

Running the earlier bash command on a semi-old commit with the time command gave the following:

0.02s user 0.01s system 99% cpu 0.028 total 

Running it on a line in a large repo where the relevant commit is over two years old gave the following

0.06s user 0.01s system 99% cpu 0.064 total

In addition, would it be possible to have it so that this runs asyncronously and updates the line blame upon success? That way any induced delay would not affect the initial line blame.