10 Best VS Code Extensions for Git and GitHub

Ten VS Code extensions that supercharge your Git workflow. GitLens, Git Graph, GitHub Pull Requests, Conventional Commits, and more.

8 min read

These 10 extensions turn VS Code into a capable Git client. They add inline blame, visual commit graphs, pull request management, and helpers that remove the friction of writing commit messages and .gitignore files. Every extension listed has a verified or well-known publisher as of mid-2026.

Git must be installed on your system for any of these to work. VS Code's built-in Git features also require Git. If you need help setting up Git in VS Code, read the guide on configuring Git and your name and email.

Repository insights

1. GitLens

Publisher: eamodio.gitlens
Why: GitLens is the most popular Git extension for VS Code. It adds inline blame annotations that show who last changed each line and when.

Hover over any line to see the full commit message, author, and date.

The free tier includes hover details and blame annotations, and the Commit Graph works on public and local repositories. Using the Commit Graph on a private repository, along with Worktrees and Visual File History, requires the paid Pro tier.

2. Git Graph

Publisher: mhutchie.git-graph
Why: A visual commit graph in its own view. See branches, merges, and commit history as a clean tree. Perform Git actions like cherry-pick, revert, merge, and branch creation directly from the graph. Click any commit to see its full diff.

While GitLens also has a Commit Graph, Git Graph is a dedicated tool that works on private repositories without a paid tier. It has had no updates since 2021, so treat it as stable rather than actively developed.

3. Git History

Publisher: donjayamanne.githistory
Why: View the history of a file, a line, or a branch in detail. Compare branches and commits side by side. Search through commit messages. Git History is more focused on exploration than inline information, making it a complement to GitLens.

GitHub integration

4. GitHub Pull Requests and Issues

Publisher: GitHub.vscode-pull-request-github
Why: Review, comment on, and merge GitHub pull requests without leaving VS Code. Browse issues assigned to you. Create pull requests from your current branch.

See CI status checks inline. This is the official GitHub extension and is maintained by GitHub.

Sign in with your GitHub account, and your PRs appear in the GitHub Pull Requests view in the Activity Bar.

5. GitHub Repositories

Publisher: GitHub.remotehub
Why: Open any GitHub repository in VS Code without cloning it first. Browse the code, make edits, and open pull requests. The repository opens in a virtual workspace. Useful for quick reviews, documentation fixes, and exploring unfamiliar codebases.

Commit helpers

6. Conventional Commits

Publisher: vivaxy.vscode-conventional-commits
Why: Helps you write structured commit messages following the Conventional Commits standard. Open the Source Control panel, type your message, and the extension provides a quick pick menu for commit types (feat, fix, docs, chore, etc.), scopes, and breaking change flags.

If your team uses semantic versioning and automated changelogs, this extension ensures every commit message follows the format.

7. Git Blame

Publisher: waderyan.gitblame
Why: A lightweight alternative to GitLens for inline blame. Shows the author and commit message for the current line in the Status Bar. Hover to see the full commit details. Good if you want blame information without the full GitLens feature set.

8. Git Automator

Publisher: ivangabriele.vscode-git-add-and-commit
Why: Adds convenient buttons for staging, committing, pushing, and pulling directly in the editor toolbar. Reduces clicks when you are making many small commits. Can be configured to auto-fetch on a schedule.

Repository setup

9. .gitignore Generator

Publisher: piotrpalarz.vscode-gitignore-generator
Why: Creates .gitignore files by selecting languages and frameworks from a list. Open the Command Palette, run Generate .gitignore, and choose what to ignore. The extension pulls templates from GitHub's gitignore repository. No more copying .gitignore files from Stack Overflow.

10. gitignore

Publisher: codezombiech.gitignore
Why: Syntax highlighting and validation for .gitignore files. It understands gitignore patterns and highlights errors. Also provides autocomplete suggestions when editing .gitignore files. Complements the .gitignore Generator by helping you maintain existing files.

Quick selection guide

If you want to...Start with
See who changed what and whenGitLens
Understand branch structure visuallyGit Graph
Review PRs inside VS CodeGitHub Pull Requests and Issues
Write better commit messagesConventional Commits
Create .gitignore files fast.gitignore Generator
Lightweight blame in the Status BarGit Blame

Each extension is free and can be installed from the Extensions view (Ctrl+Shift+X / Cmd+Shift+X). GitLens Pro is a paid upgrade needed only if you want its Commit Graph, Worktrees, or Visual File History on a private repository; everything else on this list works fully free.

For extensions that speed up everyday tasks beyond Git, see the list of 15 productivity extensions.

Rune AI

Rune AI

Key Insights

  • GitLens (eamodio.gitlens) adds inline blame, hover details, and the Commit Graph to VS Code.
  • Git Graph (mhutchie.git-graph) shows a visual commit and branch graph in its own view.
  • GitHub Pull Requests and Issues (GitHub.vscode-pull-request-github) lets you review, comment, and merge PRs from within VS Code.
  • Conventional Commits (vivaxy.vscode-conventional-commits) helps you write structured commit messages with a quick pick UI.
  • .gitignore Generator (piotrpalarz.vscode-gitignore-generator) creates .gitignore files for any language or framework.
RunePowered by Rune AI

Frequently Asked Questions

Do I need Git installed separately to use these extensions?

Yes. Every Git extension for VS Code requires Git to be installed on your system. VS Code's built-in Git support also needs Git installed. Download it from git-scm.com or install it through your package manager.

What is the difference between GitLens and Git Graph?

GitLens adds inline annotations, blame information, and repository insights directly into the editor. Git Graph gives you a visual commit graph with a dedicated view. They complement each other. Use GitLens for daily inline information. Use Git Graph when you need to understand branch structure.

Is GitLens still free?

GitLens has a free tier that includes inline blame, hover details, and the Commit Graph for public and local repositories. Using the Commit Graph on a private repository requires the paid GitLens Pro tier, along with visual file history, Worktrees, and Launchpad. If you work mostly in private repositories, Git Graph is a free alternative for the commit graph view.

Conclusion

These 10 extensions make Git feel native to VS Code. Start with GitLens and Git Graph for instant visibility into your repository's history. Add GitHub Pull Requests if your team uses GitHub. gitignore Generator and Conventional Commits remove the small friction of remembering syntax. For general productivity, see the list of 15 productivity extensions.