Skip to content
| Marketplace
Sign in
Visual Studio Code>SCM Providers>Tortue GitNew to Visual Studio Code? Get it now.
Tortue Git

Tortue Git

jcd

|
1 install
| (0) | Free
A TortoiseGit-inspired Git client for Visual Studio Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Tortue Git

Tortue Git brings the TortoiseGit workflow into Visual Studio Code. Right-click a file or folder in the Explorer to inspect its history, compare versions, or stage changes. A repository tab brings together the revision log, working tree, references, and stashes.

Tortue Git Home with a workspace repository and shortcuts for changes, history, and repository creation

This is an independent extension written in JavaScript, HTML, and CSS. It uses the Git executable on the extension host. TortoiseGit provided the workflow reference. TortoiseGit project

Install and open

  1. Install Visual Studio Code 1.85 or later and Git 2.30 or later. The git command must be available on PATH.
  2. In VS Code, open the Command Palette, run Extensions: Install from VSIX…, and select tortue-git-0.15.1.vsix.
  3. Run Tortue Git: 🏠 Open Home. Select a workspace repository, browse for another working tree, or clone a repository. The home page also provides shortcuts to review changes, browse history, and initialize a folder.

Click the turtle in a repository header to return home. In the Explorer, right-click a file or folder and open 🐢 Tortue Git. Look for 🔍 Check for Modifications, ↔️ Diff Selected Path, or ✅ Commit Checked Files…. The same symbols appear beside the commands in the Command Palette.

Use Clone Repository to clone into a new folder or Create Repository Here to initialize a folder. In a multi-root workspace, commands from the palette offer a folder picker. An Explorer selection identifies the working tree directly, including a nested repository or linked worktree.

Review and commit a change

  1. Open Working tree. Each row shows the file status and its lines added and removed relative to HEAD. Binary files show a dash. Click a path to compare the file on disk with the last commit.
  2. Check individual files or Shift-click a second checkbox to select a range in the flat list. Folders groups paths into collapsible folders. A mixed checkbox means some files in that folder are checked. Folder checkboxes act on matching descendants, including those inside collapsed folders.
  3. Filter by path or status, or click + or − to sort by lines changed. The footer counts checked files hidden by the current filters or collapsed folders. Checked only shows the selection.
  4. For a partially staged file, choose On disk or Staged blocks. The line counts, comparison and commit use that source. An Index only row offers the prepared version when the file on disk already matches HEAD. Untracked and partially staged files start unchecked.
  5. Choose Review checked files. Use Previous file, Next file or Uncheck file in the comparison. For an unsaved editor, Save & review opens the saved version. If the chosen contents change after review, reopen that file before committing.
  6. Enter a message and choose Commit checked files. Unchecked files keep their index entries. Open Revision log to inspect the new commit against its first parent.

If a Git hook formats a checked file and stages the result, the Working Tree lists the paths the hook changed. The index reflects the version recorded in the commit. Any edits made on disk afterward remain working-copy changes. The report also identifies paths the hook included outside the selection, and Tortue Git preserves existing staging for unchecked paths.

In the Explorer, ➕ Add / Stage stages new files and changes under the selected paths. 🗑️ Delete… previews the tracked files to remove. Confirm to delete them from disk and stage their removal. Git checks for local changes, and untracked files in selected folders stay on disk. 🚫 Ignore adds an exact rule to the .gitignore in the selected item's parent folder. Existing tracked files stay tracked. All three commands accept multiple selections in the same working tree.

The Explorer menu also supports unstaging and comparing selected paths. Blame File shows the author and revision for each line of the working file.

Compare files and resolve conflicts

Compact file comparison with the Git index on the left, the working copy on the right, and directional copy controls

The pane headers identify the versions being compared.

Pane Where the content comes from
Working copy The local file on disk. If its editor has unsaved changes, the pane shows that editor buffer and labels it as unsaved. Edit working file opens the editor.
Staged version The Git index. This is the content prepared for the next commit. Editing the file after staging it can leave different versions in the index and on disk.
Commit The file as recorded in the named commit. HEAD is the currently checked-out commit. Committed snapshots are read-only.

In an unstaged comparison the index is on the left and the working copy is on the right. Click Compare working copy with… to choose the index, HEAD or an earlier revision from the file's history. You can also enter a commit ID, branch or tag. The comparison opens in a new tab and follows renames detected by Git. For a file with no pending changes, Diff Selected Path in the Explorer opens the same picker.

To stage a block, click its left arrow in the working copy, then Save to Git index. To restore a block from the index or a commit, click its right arrow and choose Save to disk. Arrows appear on the active block or on hover. Shift-click or drag across differences to select several blocks together.

To copy individual lines, click a line number or drag over text within one difference. Shift-click another number to extend the range. Use the usual block arrow or Alt+Left / Right to transfer just those rows. The destination preview shows what will be saved.

If a copied source changes before you save, Refresh block updates the preview for another review. Keep displayed version saves the content you selected earlier. If the edits cross selection boundaries, Open updated comparison opens the current versions alongside your existing review.

Right-click a block to copy the selection, copy and advance, copy all remaining differences, or undo and redo a transfer. Each destination has its own save button. Closing a tab with pending transfers keeps a draft in VS Code's workspace storage. When the file and index still match, reopen the same comparison and choose Resume draft or Discard draft. After an external change, View previous draft opens the old preview or conflict choices as read-only text you can copy. Tortue Git: View Saved Review Draft in the Command Palette also works after a conflict has been resolved. Older drafts created in 0.9.0 can show only the text or transfer history that version recorded.

Shortcut Action
Alt+Left / Right Copy the selected differences toward that pane
Ctrl+Alt+Left / Right Copy and advance
Alt+Up / Down or F7 / F8 Go to the previous or next difference
Alt+Home / End Go to the first or last difference
F9 Toggle merge mode to navigate and copy with the arrow keys alone
Ctrl+Z / Ctrl+Y Undo or redo a transfer

The map at the left also lets you jump to a difference. For a comparison across revisions, select a changed file or choose the complete unified diff.

Resolve a Git conflict

  1. In Working tree, click Resolve… next to the conflicted file. Current is Git's checked-out side (stage 2). Incoming is the version being applied (stage 3). During a rebase, the incoming side is the commit being replayed.
  2. Underlined highlights identify the changed words, numbers, and punctuation on each line. For a conflict block, choose Use current, Use incoming, Use both (current first), or Edit block. Your custom draft stays available when you try another choice. Undo choice steps back through the selected block's decisions.
  3. Read Merged result below the source panes. Its selector identifies the source of each block, such as Kept from main or Edited by you. Select an entry to jump to its source and result. A labeled placeholder marks each unresolved block.
  4. When Git supplies a whole-file conflict, the buttons name the entire version or deletion to keep. You can also edit the entire file or keep its working copy. Combining both sides is available only for parsed conflict blocks.
  5. Save & mark resolved writes the preview and stages this file. If Git cannot stage it, File saved · still unresolved confirms the write. Fix the reported Git error, then select Retry staging. The retry checks the saved file and conflict entries before staging the result.
  6. After Saved and staged, the review shows how many files still need resolution. Click Resolve next file to open the next conflict. After the last file, click Finish merge to create the merge commit. For a rebase or cherry-pick, use the corresponding continue action in Repository Actions. Closing a review with pending choices keeps the choices, custom text and undo history for the same conflict.

For a binary conflict, each pane identifies the Git blob and its size. Choose the entire current or incoming version, including deletion when a side removed the file. Save & mark resolved applies the choice. Skip for now leaves the file in the conflict list and opens the next file when one is available.

For example, if Current contains timeout = 30 and Incoming contains timeout = 60, choosing Use incoming shows timeout = 60 in the result. Edit block lets you enter a different value, such as timeout = 45. The working file changes when you save the result.

Repository operations

Where Available operations
Revision log View the commit graph, filter loaded commits by author, message, reference or hash, include all branches, and load older revisions in groups of 100. Show Log on a file or folder scopes the results to that path.
Commit actions Browse files at a revision, copy a commit ID, compare revisions or the working tree, create a branch or tag at a commit, cherry-pick, revert, reset, start a bisect, and export a commit patch.
Working tree Filter changed paths, review line counts, commit checked files, discard tracked edits, resolve conflicts, and stash changes.
References Inspect local branches, upstreams, remote-tracking branches and tags. Switch local branches, track a remote branch, or merge a reference.
Stashes Apply, pop, or drop an individual stash.
Repository actions Fetch, pull, push, add remotes, merge, rebase, delete merged branches, amend a commit, apply a patch, or continue and abort operations. Inspect the reflog, manage a bisect, add a linked worktree, and initialize or update submodules.

Right-click a file or folder in the Explorer and choose 🐢 Tortue Git → ⬇️ Pull to update the current branch from its upstream. The repository toolbar and Repository Actions → Pull (Merge) run the same operation. Git fast-forwards when possible and creates a merge commit when the branches have diverged and their changes merge cleanly.

To merge another branch, right-click a file or folder and choose 🐢 Tortue Git → 🔀 Merge Branch…. Select a local or remote-tracking branch, then confirm the source and destination. The merge applies to the entire repository containing the selected path. If there are conflicts, Working tree opens so you can resolve them and finish the merge.

Choose 🐢 Tortue Git → 🔁 Switch / Checkout… to switch the selected repository to another branch. Selecting a remote branch opens its local tracking branch or prompts for a name to create one. Selecting a tag or entering a commit ID checks it out with detached HEAD. Git keeps compatible local changes and stops if switching would overwrite them.

On the first pull of a branch with no upstream, choose Track … and pull for the remote branch you want. Fetch branches from … refreshes the list for a remote. Dismissing the picker leaves tracking unchanged.

When the upstream branch has disappeared, Pull shows its name and offers replacement branches. Choose Track … and pull to change the upstream and run the pull. Dismissing the picker keeps the previous tracking configuration.

The repository header shows the current branch, its upstream, and how many commits there are to receive and send. The counts use the locally known upstream revision. Last fetch uses the update time of this working tree's FETCH_HEAD file and can reflect a fetch from any remote.

If Git finds conflicts, Tortue Git opens Working tree with the affected files. Git leaves conflict markers in text files where the edits overlap. Choose Resolve… and Save & mark resolved, or edit the file in VS Code and stage it. If a conflict still contains an opening, ancestor or closing marker, Tortue Git reports the file and line and leaves the whole staging selection untouched. During a merge, rebase, cherry-pick or revert, finish the operation with its own continue action. After resolving all files, use Finish merge in the review or Continue merge in the working tree. Abort merge… cancels the pending merge after confirmation.

Push shows the destination and can establish an upstream on the first push. Git uses its configured credential helper or SSH setup.

For bisect, select a known-bad commit, choose a known-good ancestor, then mark each checked-out revision good or bad in Actions…. Finish the bisect to return to the original checkout.

Scope

The extension targets the desktop VS Code Explorer and editor. It includes a WinMerge-inspired comparison and conflict review for UTF-8 text and whole-file choices for binary conflicts. Use a suitable external tool for symlink or submodule conflicts, then stage the resolved path. Windows shell overlays, TortoiseGit settings import, Git LFS management, and SVN bridge commands are outside this release. History scoped to a path uses its current name. A merge commit's file list is relative to its first parent. Git output for a single operation is limited to 32 MiB.

Develop

Open this folder in VS Code and press F5 to launch an Extension Development Host. Open a Git working tree there and run Tortue Git: 📂 Open Repository. The extension runs directly from source, with no build step or runtime npm dependencies.

File Responsibility
package.json VS Code commands, menus, activation entry point, and extension metadata
src/extension.js Repository discovery, command registration, and panel lifetime
src/git.js Git process execution, status parsing, history, revision details, and index updates
src/panel.js Messages between the webview and the extension, serialized operations, and refresh
src/actions.js, src/revisionActions.js Git workflows and native VS Code prompts
src/fileCommands.js, src/documents.js Explorer selections, file previews, blame, and read-only diff documents
src/reviewPanel.js, src/fileComparison.js, src/comparisonSession.js, src/conflict.js Review tabs, line alignment, pane snapshots and saves, and Git conflict resolution
media/merge-model.js The same per-block choices used to construct the preview and the saved result
media/ Webview markup, theme-aware styles, graph drawing, and DOM events

Run the integration tests with Node.js 20 or later and Git on PATH. The tests create and remove temporary repositories.

npm test

To rebuild the installation package with the VS Code packaging tool, run the following with a current Node.js LTS installation.

npx @vscode/vsce package --no-dependencies
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft