The everyday toolkit for Salesforce developers. Deploy one file or everything committed since the last release, check a change against an org without saving it, run Apex tests, refresh the pipeline's org logins, and export Confluence pages to Markdown, all from inside VSCode. Problems show up before a change is committed, while they are still cheap to fix.
Lists every org you are signed in to. Click the swap icon to make one active. The active org's alias shows in the status bar, and clicking it switches orgs without opening the panel.
Shows the files you have changed but not yet committed, grouped as modified, added, deleted, renamed and untracked, so you can see what a commit would include.
Deploys the file open in the editor to the active org. Prompts for Deploy or Validate. Best when you are working on one component.
Sends everything committed since the last deployed/<env> tag in one go. In a project set up by Pipeline Manager, it runs the pipeline's own delta script against the active org instead.
Right-click a file or folder in the explorer to deploy that path. Handy for pushing a whole feature folder at once.
Export a Confluence space to Markdown files, ready to commit next to your metadata, where the Data Dictionary can show them inside Salesforce. It runs inside the extension, with no Python or other tools to install. A four-step wizard lets you pick exactly which pages to export before it starts.
It has its own panel in the extension's sidebar. Click the icon to open the wizard. Your Confluence API token is saved in VSCode's encrypted secret storage and reused next time. The output folder is emptied before each run, so pick a folder that holds nothing but the export.
The commands above cover the daily loop of deploy, validate and test. The command palette has more: switching orgs, checking test coverage, retrieving metadata, generating package.xml, and the pipeline setup commands.
| Command | What it does |
|---|---|
| SF Dev: Switch Active Org | Quick pick across all authenticated orgs |
| SF Dev: Deploy Current File to Org | Deploys the open file, prompts Deploy/Validate |
| SF Dev: Deploy to Org | Right-click file/folder, prompts Deploy/Validate |
| SF Dev: Deploy Changed Files (Delta) | Deploys everything committed since the deploy tag, through the pipeline's delta script when the project has one |
| SF Dev: Validate Deploy (Check Only) | Check-only run of the whole force-app directory |
| SF Dev: Run All Apex Tests | Runs all local tests; results in the output panel |
| SF Dev: Run Apex Tests for Current File | Runs the test class that is open in the editor |
| SF Dev: Check Test Coverage | Reports org-wide and per-class Apex coverage |
| SF Dev: Retrieve Metadata from Org | Pulls metadata using retrieve.xml or force-app |
| SF Dev: Set Up CI/CD Pipeline | Quick pipeline setup for one org and one branch |
| SF Dev: Add Pipeline Environment | Adds an org and branch to the pipeline settings |
| SF Dev: Rotate Pipeline Credentials | Refreshes expired SFDX auth URLs: through the API for Bitbucket and GitLab, through the gh CLI for GitHub, and as a new value to paste in for Azure DevOps and Jenkins |
| SF Dev: Enable Bitbucket Pipelines | Turns on Bitbucket Pipelines via REST API |
| SF Dev: Generate package.xml | Runs sf project generate manifest on the source directory |
| SF Dev: Initialise Deploy Tag | Creates deployed/<alias> tags at HEAD to set the delta baseline |
| SF Dev: Export Confluence Space | Opens the four-step Confluence export wizard |
Check every change against a real Salesforce org before anyone else sees it. The tooling is built around that habit.
Edit Apex, LWC, flows or any other Salesforce metadata in the editor as usual.
The org checks your whole force-app folder, uncommitted edits included, without saving anything.
Read the results in the output panel and fix anything it flags before the change goes any further.
Once validation passes, commit and push. The CI/CD pipeline then checks or deploys the change, depending on the branch.
The first release had the core deploy, validate and test commands. The rest followed within a week: the Deploy or Validate choice, the pipeline setup and login commands, then Confluence export and its improvements.
Confluence Export improvements: four-step wizard with a page-selection tree (Select All / Deselect All), clear-before-export to drop stale pages, attachment CDN redirects followed, saved token accepted at validation, and esbuild bundling to keep node_modules out of the VSIX.
Confluence Export: three-step webview wizard exports any space to Markdown with images. Encrypted token storage, HTTPS only, and a check that rejects localhost and private IP addresses as the Confluence URL.
Add Pipeline Environment, Rotate Pipeline Credentials, Enable Bitbucket Pipelines, Generate package.xml, Initialise Deploy Tag.
Pipeline setup wizard: auto-fetches auth URLs, registers them via the provider REST API, and writes the pipeline files and scripts.
Deploy mode picker on every deploy command: Deploy or Validate (check-only).
Initial release: Connected Orgs panel, Changed Files panel, status bar, and the deploy / validate / test / retrieve commands.