Subversion Workbench for Visual Studio Code
Modern Subversion integration for everyday development in VS Code, including large working copies and multi-root workspaces. Highlights
RequirementsThe extension uses your local SVN command-line client and supports SVN 1.6 or newer. On Windows, TortoiseSVN users must install Command Line Tools and make
InstallationThe distinct Marketplace identity for this maintained fork is
For manual or offline installation, see Installing from a VSIX. Disable another SVN SCM extension if it registers the same working copies, to avoid duplicate Source Control providers. Everyday workflowsCheckoutRun SVN: Checkout from the Command Palette ( Stage and commitThe Source Control view separates Changes from Staged Changes. Stage individual files or folders, use Stage All Changes, and commit the selected set with Commit Staged. Only files in Staged Changes are committed. When multiple opened workspace folders belong to one physical working copy, their visible changes are combined in one Source Control provider and staged paths can be committed together. Resolve conflictsSelect a text-conflicted file in Source Control to open VS Code's three-way Merge Editor. The file remains conflicted in SVN until the result is saved without conflict markers and explicitly or automatically marked resolved. Tree, property, or incomplete text conflicts open in the normal editor and retain the explicit SVN resolution commands. Inspect history and incoming changesThe former Repositories pane is no longer shown in the Subversion activity area. Repository history is now available as SVN History directly in the standard Source Control view. File History and Branch Changes remain in the Subversion activity area and related context-menu workflows. Text-log search streams results into a document and can be cancelled from its progress notification or by closing that document. Remote status checks may contact the server and run only when requested or when remote polling is enabled. Incoming changes can be inspected and updated from the repository tree. Work with large working copiesOn startup, the extension can restore the previous changes list while SVN validates the working copy in the background. Small known edits are checked early, while a full status scan remains the correctness fallback. Normal file events and local SVN operations use targeted refreshes when safe. SettingsChange settings in the VS Code Settings UI or in
Limitations
Feedback and contributing
Project historySubversion Workbench is an independent maintained fork of JohnstonCode/svn-scm, with its own Marketplace identity and branding. It is not affiliated with or endorsed by the original publisher. See the original contributors. The existing |