Tortue GitTortue 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.
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
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
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 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
The pane headers identify the versions being compared.
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.
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
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 Repository operations
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 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. ScopeThe 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. DevelopOpen 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.
Run the integration tests with Node.js 20 or later and Git on PATH. The tests create and remove temporary repositories.
To rebuild the installation package with the VS Code packaging tool, run the following with a current Node.js LTS installation.
|

