By the way, when you click on the bottom toolbar, a dialog will pop up giving it tons of options, like opening a commit in GitHub or open a revision of this file with this commit.This post will discuss some of my favorite features of the GitLens VSCode extension that might help you optimize your git workflow in VSCode. As you can see, the notation is not visible anymore, but the bottom toolbar still is. You can do this by opening the UI settings, filter by GitLens current line, and deactivate the option. If you do two, I recommend turning off the current line limitation but keeping the bottom bar. Personally, I don't need the commit information all the time and I'd rather prefer a cleaner editor view. Select the commit and see which parts of the file were manipulated with the same commit. If this is yet not enough, you can activate the Blame limitation for the whole file with the icon on the top right. Having the information who wrote the line and when provides a lot more context to help you making better decisions. Having this information is especially great if encountering a line with a purpose you don't understand and potentially want to change it. The same information will also be available in the bottom toolbar. On the next line, changes three months ago. If you hover over it, you also can see further details of this commit.

Here, you can see where I made a change five month ago. Once you install gitlens, you will see an annotation next to every line. In my case, I'm opening the tooltip implementation of the read GI library. Then, let's open a file inside a Git repository. Instructor: Let us install the VS Code extension, Gitlens.

What is visual studio code lens