Git Navigator Pro
A lean, full-featured Git sidebar for VS Code. Stage and commit, browse an interactive
commit graph, stash, diff, blame, resolve conflicts, work across multiple repos, manage
tags and branches, and handle pull requests — without leaving the editor or memorising
terminal commands.
Standard Git terminology, no AI, everything runs locally against your system Git.
Install
From the VS Code Marketplace:
Or in VS Code: Extensions (Ctrl+Shift+X) → search Git Navigator Pro → Install.
Requirements
- Visual Studio Code 1.80.0 or newer
- Git installed and on your
PATH
- GitHub sign-in (VS Code's built-in auth) only if you create or review pull requests
Screenshots live in media/ — add panel captures here before publishing.
What you get
Changes panel
- Staged / unstaged split with per-file status badges
- Click a file to diff it against HEAD; stage, unstage, discard (with confirm), open
- Stage All / Unstage All, inline commit box (
Ctrl+Enter), and an Amend checkbox
- A Merge Conflicts section: Accept Current, Accept Incoming, or open the merge editor
- Context-aware Sync button showing ahead/behind
Commit Graph
- Lane-based history with branch/tag/HEAD badges and relative dates
- Click a commit to view it; an uncommitted-changes row jumps to the Changes panel
- Right-click a commit: copy hash, view, compare with working tree, create branch/tag
here, cherry-pick, merge, revert, checkout, or reset (keep / discard changes)
Daily verbs (Actions view + command palette)
- Stash (push / pop / manage), Fetch, Push (sets upstream when needed)
- Amend, Undo last commit, Revert, Abort merge/rebase
- Checkout / merge / delete / rename branches, Manage Tags
Authorship
- Toggle inline line blame (
Ctrl+Alt+B) for the current line
- File history (
Ctrl+Alt+H) and "open the commit for this line"
More
- Compare branches, search commits
- Multi-root: repos are discovered across folders; a status-bar picker switches the active one
- Pull Requests: list open PRs, check one out locally, or browse its changed files
- Create a Pull Request via VS Code's GitHub sign-in (no token needed)
Quick start
- Open a folder. If it isn't a repo yet, the panel offers Set Up Repository / Clone.
- Open the Git Navigator icon in the Activity Bar.
- Make changes, stage them in the Changes panel, write a message, and commit.
- Push from the Actions view (it sets the upstream the first time).
Settings
| Setting |
Default |
What it does |
gitNavigator.graph.pageSize |
50 |
Commits the Graph loads per page |
gitNavigator.commit.template |
"" |
Text prefilled into the commit prompt |
gitNavigator.blame.enabledOnStartup |
false |
Turn line blame on at activation |
gitNavigator.confirmDiscard |
true |
Confirm before discarding changes |
gitNavigator.alwaysShowActions |
false |
Always show row actions (keyboard / screen-reader friendly) |
Keybindings
Ctrl+Alt+B — Toggle Line BlameCtrl+Alt+H — File History (when an editor is focused)
Troubleshooting
- No repository found: use Set Up Repository, or open a folder that contains
.git.
- Pull / clone issues: confirm
git --version works in your terminal.
- PR actions fail: make sure
origin is a GitHub URL and you're signed in to GitHub.
Privacy and security
- Git operations run locally with your system Git.
- GitHub auth uses VS Code's built-in provider; no personal access token is stored by the
extension.
- Clone/remote URLs and branch names are validated before reaching Git, and credentials
are stripped from any surfaced error messages.
License
MIT
| |
