G2

Yash D.

Senior Software Engineer II

Computer Software

Mid-Market (51-1000 emp.)

5/11/2026

"GitLens in VS Code: Instant Blame, Clean AI Commit Messages, and a Great Commit Graph"

4.5/5

What do you like best about GitLens?

- This is a lifesaver. Being able to see who modified a specific line of code, along with the commit message, directly in the editor saves me from constantly jumping back to the terminal or GitHub.

- I’ve started using the AI Commit Explanations to draft my commit messages. Since I work across Python and JS, it’s nice to have a consistent, descriptive summary of my changes generated automatically, which I then just quickly polish. It keeps our Git history much cleaner for the rest of the team.

- It is easy to integrate this using the GitLens extension in the VSCode IDE.

- With the Commit Graph UI, I can visually trace how a feature branch was merged or rebased without leaving VS Code. Review collected by and hosted on G2.com.

What do you dislike about GitLens?

Regarding performance, the commit graph sometimes takes a few extra seconds to index several thousand commits, which can feel a bit laggy. Aside from that, I don’t have any complaints. Review collected by and hosted on G2.com.

What problems is GitLens solving and how is that benefiting you?

It solves the context-switching problem. Instead of jumping between the terminal, GitHub, and my IDE, everything is centralized in one place. It’s especially helpful for collaborative code reviews, because I can see the intent behind a line of code immediately. For our team, it has improved our development speed since we spend less time manually tracing Git history and more time actually shipping code. Review collected by and hosted on G2.com.