
GitLens
Git supercharged
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 is an open-source extension for Visual Studio Code created by Eric Amodio.
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. 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 GitLens Settings editor, an interactive editor covering many of GitLens' powerful settings. While for more advanced customizations, refer to the GitLens docs and edit your User Settings.
Don't miss how easy it is to configure GitLens!
What's New in GitLens 9
See the release notes for the full set of changes
- 9.0 DEC 2018
-
NEW Adds GitLens over
Visual Studio Live Share
Live Share guests will now have read-only access to GitLens' features, provided both the host and guest have GitLens installed
-
NEW Adds a new Git
virtual file system provider for the
gitlens:
scheme — closes #430Replaces GitLens' internal handling of file revisions, which allows for better performance, as well as avoiding the use of temp files. It also provides a much better experience when dealing with file encodings, images, etc.
- NEW Adds an Explore the Repository from Here command which opens a virtual workspace folder (using the new Git virtual file system provider) for the repository at the specified point in time (commit, branch, tag, etc) — closes #398
-
NEW Adds a new
Repositories view, formerly the GitLens view, to visualize, navigate, and explore Git
repositories — closes
#456,
#470,
#494
Provides a cleaner information-rich view of your opened repositories, more git commands (fetch, push, pull, checkout, stage, unstage, etc), better visibility and accessibility of existing features, and more
-
NEW Adds a new
File History view, formerly the History view, to visualize, navigate, and explore the
revision history of the current file
Provides similar features to the former History view as well as quickly toggling file tracking on and off, changing the base (branch, tag, commit, etc) of the file's history, and more
-
NEW Adds an all-new
Line History view
to visualize, navigate, and explore the revision history of the selected lines of
current file — closes
#354
Provides similar features to the File History view including quickly toggling line tracking on and off, changing the base (branch, tag, commit, etc) of the selected lines' history, and more
-
NEW Adds an all-new
Search Commits view
to search and explore commit histories by message, author, files, id, etc —
closes
#455
Provides somewhat similar features to the former Results view as well as it is now a persistent view, makes it easier to start a commit search, and more
-
NEW Adds an all-new
Compare view
to visualize comparisons between branches, tags, commits, and more
Provides somewhat similar and powerful features to the former Results view as well as it is now a persistent view, makes it easier to start a comparison, and more
- NEW Reduces the overhead of all GitLens views — GitLens now only tracks changes and updates the views if they are visible, collapsed or hidden views should have almost zero overhead
- NEW Adds relative date markers (Less than a week ago, Over a week ago, Over a month ago, etc) to revision (commit) histories in GitLens views
- NEW Adds branch and tag tip markers to revision (commit) histories in GitLens views — closes #560
- NEW Adds a changes indicator (+x ~x -x) to commits in GitLens views — closes #493
-
NEW Adds comparisions
to commit ids, by prefixing with a
#
, in addition to branches and tags — closes #535 - NEW Adds support for git mailmap — closes #388
- NEW Adds support for Azure DevOps (formerly VSTS) remotes — closes #501
- NEW Adds better detection of on-prem BitBucket and GitLab remotes — closes #214
- NEW Adds some missing gitmojis — thanks to PR #510 by Loris Bettazza (@Pustur)
- IMPROVED Changes the sorting of branch, tags, and files in GitLens views to be a natural sort #547
- IMPROVED Changes the Apply Changes command to truly apply only the patch of the specified change #539
- FIXED Fixes #405 — Secondary, blank repository appears repeatedly in Repositories view
- FIXED Fixes #430 — File revisions can end up being parsed by language servers (causing errors and warnings, etc)
- FIXED Fixes #496 — Short hash length doesn't match git's default length
- FIXED Fixes #503 — Open Changes (with difftool) opens one difftool window per changed file
- FIXED Fixes #507 — Restrict commit message size
- FIXED Fixes #527 — GitLens icon flashes on startup
- FIXED Fixes #533 — Some descriptions not using markdown properly in Settings GUI
- FIXED Fixes #544 — Some commit messages have one letter missing