We clicked on line 11 and in the bottom strip we will see the author of that line. To illustrate what this looks like, we have opened the same Community.js file, which we have checked from the terminal. Now we can open any file and click on any line. We don’t need to do any other configurations to use this extension. Once installed successfully, we will see the Disable and Uninstall buttons. After that, click on the Install button to install this extension in your VS Code. We will get a lot of extensions, but click on the first one, which is Git Blame by Wade Anderson and has 1.3 million downloads. Here, search for “blame” in the input box and press Enter. After that, we need to click on the Extension tab in the left strip. You can open any project, but it will be useful if the code has multiple authors. We have opened our earlier project in VS Code. We will look at the below extensions to add git blame to our project: These extensions are generally small programs that add functionalities in VS Code. Now, most extensions in VS Code are free to use like VS Code itself. Instead, we can use four extensions in VS Code, which will help us find the author of each line of code easily. VS Code Git Blame ExtensionsĪs we just saw, it is a lot of work to manually check the author in each file through the command line. In the next section, we are going to look into better ways to do this through VS Code extensions. So, it will be very difficult to check the different authors in each file through the command line. The above project is a large React.js project with many files. We can also see that almost all changes were done by a user called ankit, but the change on line 16 was made by user nabendu82. Here, the author of each line is mentioned.

Notice that we have to give the complete path and also the filename.

In the below example, we are using git blame to find the changes done in a file.

Git in visual studio code