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.8

  • 9.8.2 JUNE  2019
  • NEWAdds a changes indicator (+x -x) to the File History view to quickly show the number of added and/or deleted lines
  • IMPROVEDPreserve Show More expansions during file system or repository changes — avoids losing view expansion and selection
  • IMPROVEDChanges to match authors exactly in the Contributors view
  • FIXEDFixes #734 — Not working with VS Code Remote - SSH extension (fixes the broken hover image)
  • FIXEDFixes #751 — Git Command failed
  • FIXEDFixes #756 — Merge commit shows only the changes from the last commit on those files
  • FIXEDFixes issue with the Open Changes with Previous Revision command when run from the diff editor and the file has unstaged changes
  • FIXEDFixes an issue where view expansion and selection was getting lost with search and compare nodes
  • 9.8.1 MAY  2019
  • FIXEDFixes the Show More command in the File History and Line History views
  • FIXEDFixes a caching issue with file histories
  • FIXEDFixes a regression where the Copy Remote Url to Clipboard command fails to include the selected line range
  • 9.8 MAY  2019
  • NEWAdds a new Compare Current Branch with <branch, tag, or ref> node to each repository in the Repositories view — closes #293

    Optionally shows a comparison of the current branch to a user-selected reference

  • NEWAdds a new experimental Incoming Activity node to each repository in the Repositories view (enabled via "gitlens.insiders": true) — closes #735

    Lists the recent incoming activity (merges and pulls) to your local repository. Provides the command, branch (if available), and date of each activity

  • NEWAdds a Show a comparison of the current branch to a user-selected reference (gitlens.views.repositories.showBranchComparison) setting to specify whether to show a comparison of the current branch to a user-selected reference in the Repositories view
  • NEWAdds a gitlens.advanced.useSymmetricDifferenceNotation setting to specify whether to use the symmetric difference (three-dot) notation or the range (two-dot) notation for comparisions — closes #330
  • NEWAdds a Copy Remote Url to Clipboard command to commit quick pick menus
  • IMPROVEDChanges Pull and Pull Repositories commands to just fetch the repository if the current branch has no tracking branch
  • FIXEDFixes #734 — Not working with VS Code Remote - SSH extension
  • FIXEDFixes #739 — Breadcrumbs don't work on file revisions
  • FIXEDFixes #750 — Open file on GitHub does not include directory path
  • FIXEDFixes an issue with the Open Revision command in the quick pick menus not working properly

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