<atitle="Learn more about GitLens"href="https://gitlens.amod.io"><imgwidth="476px"src="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/gitlens-logo-anybg.png"alt="GitLens Logo"/></a>
<atitle="Learn more about GitLens"href="https://gitkraken.com/gitlens"><imgwidth="476px"src="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/gitlens-logo-anybg.png"alt="GitLens Logo"/></a>
</p>
> GitLens **supercharges** Git inside VS Code and unlocks **untapped knowledge** within each repository. It helps you to **visualize code authorship** at a glance via Git blame annotations and CodeLens, **seamlessly navigate and explore** Git repositories, **gain valuable insights** via rich visualizations and powerful comparison commands, and so much more.
@ -18,14 +19,14 @@
</p>
<palign="center">
<atitle="What's New in GitLens 12"href="https://www.gitkraken.com/blog/gitlens-12-1"><imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/whats-new-button.png"alt="Open What's New in GitLens 12"/></a>
<atitle="What's New in GitLens 12"href="https://gitkraken.com/blog/gitlens-12-1"><imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/whats-new-button.png"alt="Open What's New in GitLens 12"/></a>
<br/>
or read the <ahref="https://github.com/gitkraken/vscode-gitlens/releases/latest">release notes</a>
</p>
# GitLens
[GitLens](https://gitlens.amod.io 'Learn more about GitLens') is an [open-source](https://github.com/gitkraken/vscode-gitlens 'Open GitLens on GitHub') extension for [Visual Studio Code](https://code.visualstudio.com).
[GitLens](hhttps://gitkraken.com/gitlens 'Learn more about GitLens') is an [open-source](https://github.com/gitkraken/vscode-gitlens 'Open GitLens on GitHub') extension for [Visual Studio Code](https://code.visualstudio.com).
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.