The setup tool. One person answers a few questions once per project and gets a complete, working release pipeline. Nobody has to read platform manuals, hand-write YAML files or keep track of which secrets go where. A four-step wizard writes every pipeline file for the chosen CI platform. Afterwards, a panel in the editor shows how the pipeline is set up.
Four steps take you from choosing a platform to a finished pipeline. The wizard can also write cicd-pipeline.md, a guide that explains the branch strategy, the developer workflow, the secrets and branch protection, so the whole team knows how releases work.
GitHub Actions, Azure DevOps, GitLab CI/CD, Jenkins, or Bitbucket Pipelines. The wizard writes the right file, in the right place, for the one you choose.
Match each environment to a Salesforce org. The usual set comes pre-filled: Dev, SIT, QA, UAT, Staging and Production. While check-only validation is on (the default), feature branches are checked against Dev on every push, before a pull request merges them. Two optional switches go further. One creates and pushes a Git branch for every environment. The other requests a Developer sandbox for each non-production environment (sf org create sandbox --async) once the files are written.
Set the source folder (force-app by default), turn check-only validation on feature branches on or off, and choose whether Apex tests run after every release, with an automatic rollback if they fail. The Generate CI/CD documentation switch writes the cicd-pipeline.md guide to a folder you pick.
Preview everything before it is created, with the files on the left and the secrets you need on the right. Click Generate Files, and the pipeline file, scripts, manifests and ci-config.json are written to the project in one go.
A panel in the editor shows the platform the pipeline runs on, every environment, the secrets it needs, and whether each generated file is present. It reads ci-config.json and updates whenever that file changes.
The + button opens the setup wizard, and the refresh icon reloads the panel. Hover over an environment and click the bin icon to remove it.
Most of what the wizard and the panel do is also a command, for anyone who prefers the keyboard.
| Command | What it does |
|---|---|
| SF CICD: Initialize New Pipeline | Opens the four-step setup wizard |
| SF CICD: Add Environment | Quick prompt to add an environment to an existing config |
| SF CICD: Remove Environment | Not in the palette. In the panel, hover over an environment and click the bin icon |
| SF CICD: Edit Deploy Options | Change deploy settings without re-running the wizard |
| SF CICD: Regenerate Pipeline Files | Rebuild all pipeline files from the current ci-config.json |
| SF CICD: Validate Configuration | Check that ci-config.json can be read and that the pipeline file, manifests and scripts exist |
| SF CICD: Show Secrets Checklist | List the CI secret names needed for the configured environments |
Seven releases in ten days, from the first wizard to automatic branch and sandbox creation, then a generator that writes the team's CI/CD guide alongside the pipeline.
Generate CI/CD documentation toggle in Step 3: writes a cicd-pipeline.md covering branch strategy, developer workflow, secrets reference and platform-specific branch protection. Output folder chosen via the native VSCode picker.
Step 2 now tells developers to raise a pull request from their feature branch into dev, and that CI validation must pass before the merge is approved.
Dev added as the default first environment; feature branches now validate check-only against Dev rather than a scratch org, so each PR is checked against the Dev org before it merges. SCRATCH_AUTH_URL no longer required.
Create Git Branches and Create Salesforce Sandboxes toggles in Step 2: branches pushed and sandbox requests submitted automatically after file generation.
Two-column review layout in Step 4: generated files and required secrets shown side by side for an easier pre-flight check.
Remove Environment, Edit Deploy Options, and Regenerate Files from ci-config.json without re-running the wizard.
Initial release: four-step wizard, activity bar panel, ci-config.json IntelliSense, validate configuration, secrets checklist, and a getting-started walkthrough.