What's New 📣 Features About Blog

GitLens is an open-source extension for Visual Studio Code, created by Eric Amodio.

GitLens supercharges the Git capabilities built into Visual Studio Code. It helps you to visualize code authorship at a glance via Git blame annotations and code lens, seamlessly navigate and explore Git repositories, gain valuable insights via powerful comparison commands, and so much more.

GitLens simply helps you better understand code. Quickly glimpse into whom, why, and when a line or code block was changed. Jump back through history to gain further insights as to how and why the code evolved. Effortlessly explore the history and evolution of a codebase.

Support GitLens

While GitLens is generously offered to everyone free of charge, if you find it useful, please consider supporting it.

Sponsored by

marketplace downloads rating slack

Support GitLens

Sponsored by

While GitLens is generously offered to everyone free of charge, if you find it useful, please consider supporting it.

Also please write a review, star me on GitHub, and follow me on Twitter.

I've been building GitLens in my “spare”1 time for well over 2 years now. From its very humble beginnings, GitLens has grown wildly beyond my expectations — in both its reach as well as its demands on my time and attention.

To my incredible backers — thank you so much for your contributions. I am truly humbled by your generosity and support.

What's new in GitLens 9.9

  • 9.9.2 AUGUST  2019
  • NEWAdds a Checkout command to the current branch in the Repositories view which opens a quick pick menu to choose a new branch to checkout to
  • FIXEDFixes #806 — file diff in two-dot branch compare should only show the changes in one branch
  • FIXEDFixes #756 — Merge commit shows only the changes from the last commit on those files
  • FIXEDFixes #809 — Wrong commit diff in file history
  • FIXEDFixes #685 — GitLens not loading for a single repository
  • FIXEDFixes #789 — Line blame annotations not working when vscode root is home dir and .gnupg dir is inaccessible
  • FIXEDFixes #649 — GitLens can't see the remote but git can
  • FIXEDFixes #798 — git pull/fetch all repositories
  • FIXEDFixes #805 — Version 9.9.1 breaks working tree comparison
  • FIXEDFixes an issue where the GitLens Compare view was shown when using the Select for Compare command in the Repositories view
  • 9.9.1 JULY  2019
  • FIXEDFixes #797 — Branch diff against master shows incorrect files in two-dot mode
  • 9.9.0 JULY  2019
  • NEWAdds guided (step-by-step) access to common Git commands (and their flags) via the all-new Git Commands command (gitlens.gitCommands)
    Quickly navigate and execute Git commands through easy-to-use menus where each command requires an explicit confirm step before executing Git Commands
  • NEWAdds Open All Changes, Open All Changes with Working Tree, Open Files, and Open Revisions commands to files changed nodes in the views — closes #760
  • NEWAdds working tree comparison support to the Compare Current Branch with <branch, tag, or ref> node within each repository in the Repositories view

    Adds a Switch to Working Tree Comparison command or Switch to Branch Comparison command to the Compare Current Branch with <branch, tag, or ref> node

    Changes gitlens.views.repositories.showBranchComparison to also specify the default type of comparison — either with the current branch or the working tree

  • NEWAdds Switch to Two-dot Comparison and Switch to Three-dot Comparison commands to specify whether to use the symmetric difference (three-dot) notation or the range (two-dot) notation for the comparison — applies to all comparisons in the views
  • NEWAdds a new ${tips} format token to show an indicator if the commit is a tip of any branches or tags — closes #792
  • IMPROVEDImproves performance and memory consumption
  • IMPROVEDChanges the Checkout command on remote branches to create and checkout a new local branch rather than checkout a detached HEAD — closes #709
  • IMPROVEDChanges folders in the views to expand by default when using Tree Layout
  • FIXEDFixes #791 — Notification of unstashed changes in working directory on failed checkout
  • FIXEDFixes #795 — Commit quick access icons replaced with open file actions in File History View
  • FIXEDFixes issue with the JSON schema of a configuration setting

GitLens Features

GitLens simply helps you better understand code. Quickly glimpse into whom, why, and when a line or code block was changed. Jump back through history to gain further insights as to how and why the code evolved. Effortlessly explore the history and evolution of a codebase. Dive right in and see how GitLens can help!

While GitLens is powerful and feature rich, it is also highly customizable to meet your specific needs — find code lens intrusive or the current line blame annotation distracting — no problem, it is quick and easy to turn them off or change how they behave via the built-in settings editor , an interactive editor covering many of GitLens' powerful settings. While for more advanced customizations, refer to the GitLens settings docs and edit your user settings.

Here are just some of the features that GitLens provides,

  • an unobtrusive current line blame annotation at the end of the line with detailed blame information accessible via hovers
  • on-demand gutter blame annotations, including a heatmap, for the whole file
  • authorship code lens showing the most recent commit and # of authors to the top of files and/or on code blocks
  • on-demand gutter heatmap annotations to show how recently lines were changed, relative to all the other changes in the file and to now (hot vs. cold)
  • on-demand recent changes annotations to highlight lines changed by the most recent commit
  • a status bar blame annotation showing author and date for the current line
  • many rich Side Bar views
    • a Repositories view to visualize, navigate, and explore Git repositories
    • a File History view to visualize, navigate, and explore the revision history of the current file
    • a Line History view to visualize, navigate, and explore the revision history of the selected lines of current file
    • a Search Commits view to search and explore commit histories by message, author, files, id, etc
    • a Compare view to visualize comparisons between branches, tags, commits, and more
  • many powerful commands for exploring commits and histories, comparing and navigating revisions, stash access, repository status, etc
  • supports user-defined modes for quickly toggling between sets of settings
  • and so much more

About GitLens

GitLens started back in mid-2016, when I fell in love with Visual Studio Code and wanted to play with the newly released extension support. It was also a good excuse for me to improve my budding TypeScript skills. It all started with a simple question — could I add code lens showing Git insights to any document.

Since then, GitLens has quickly grown from a prototype to a full-fledged product with a mission of its own — make developers lives easier. GitLens strives to simply help you better understand code.

Read the reviews to see what people are saying about GitLens. I am truly humbled by the love and support of the Visual Studio Code community.

❤ My favorite review