HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gitkraken
vscode-gitlens
TypeScript2017–2025
gitkraken / vscode-gitlens

vscode-gitlens

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — 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

11Distinct people
11Mentions
1Explicit recommenders
10KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — 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

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Would gitlens help? I love it. https://github.com/eamodio/vscode-gitlens

swozey used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2017-07-05 23:49:51 UTC to 2025-05-29 10:04:25 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

11 sources
Weird that you couldn't get extensions working. Everything I've wanted works in vscodium. The only thing I couldn't get working is the remote sharing where you can connect to someone else's instance and co-edit (remote ssh editing works). Extensions that I currently have installed: * https://github.com/alefragnani/vscode-bookmarks * https://github.com/gitkraken/vscode-gitlens * https://github.com/redhat-developer/vscode-xml * https://github.com/redhat-developer/vscode-yaml * https://github.com/znck/grammarly * https://github.com/VSCodeVim/Vim * https://github.com/mousavian/ssh-config-syntax-highlighter * https://github.com/golang/vscode-go * https://github.com/prettier/prettier-vscode * https://github.com/braver/vscode-solarized
In The Loneliness of the Mid-Level Vimmer
I think the audience here is missing that the code diffs are included in the markdown below, probably because you need to scroll to see them. See around 3:38: https://app.paircast.io/replay/fa41d539-aea0-4d62-a192-3cd77... Because the Paircast git commits include a timestamped link to the video, using something like gitlens in VS Code would allow you to click from code to video. https://github.com/eamodio/vscode-gitlens#autolink-settings
In Document your code just by hitting “record”
Seems like optimizing the wrong thing... As a developer I'm not sitting down an typing constantly like some bad Hollywood "hacker" montage, or a court reporter. So preemptively optimizing a tiny subset of my workflow really doesn't offer much value. Contrast that with something like Chrome Debugging for VS Code[0] or GitLens[1] that are fitting into what I actually spend a lot of time doing, therefore improving productivity. If my typing was 50% faster my overall productivity would be maybe 5% better, because that just isn't a bottleneck. I feel like the vim/emacs crowd experiences professional programming VERY differently to anywhere I've worked. Myself nor any of my colleagues are just type-type-type. I spend more time reading and writing OneNote documentation files (specs, etc) than I do writing code. I spend more time in meetings than
Read the rest
I do writing code. I spend more time debugging and testing than I do writing code. [0] https://code.visualstudio.com/blogs/2017/12/20/chrome-debugg... [1] https://github.com/eamodio/vscode-gitlens
In Keep VS Code from Becoming an IDE
> I don't understand why these electron editors are popular at all. IMHO it's the future of IDE's. After years of using vi and Intellij IDEA, I've switched to VS code (which is electron based) and never looked back. I find it as snappy as vi or sublime. I feel more productive because of all the plugins. For e.g. the fantastic https://github.com/eamodio/vscode-gitlens Extending it is really easy using the language server protocol http://langserver.org/ . Our team spent very little effort to build a plugin for our open source project https://github.com/getgauge/gauge-vscode Electron editors are successful because it's hackable and cross-platform allowing the community to extend and add an impressive list of plugins.
In Xray – An experimental next-generation Electron-based text editor

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.