The setup tool. One person answers a short series of questions once per project and gets a complete, working release pipeline, instead of reading platform manuals, hand-writing YAML and tracking which secrets go where. A four-step wizard generates every pipeline file for the chosen CI platform, and afterwards a panel in the editor shows the live state of the pipeline so it stays easy to look after.
From platform choice to a finished pipeline in four steps. Alongside the pipeline itself, the wizard can write a cicd-pipeline.md documenting branch strategy, developer workflow, secrets and branch protection, so the whole team understands how releases work.
GitHub Actions, Azure DevOps, GitLab CI/CD, Jenkins, or Bitbucket Pipelines. The wizard generates the right file path and syntax for whichever you choose.
Map each environment to a Salesforce org alias. The wizard arrives pre-filled with the usual set: Dev, SIT, QA, UAT, Staging and Production. Feature branches validate check-only against Dev, so a pull request must pass CI before it merges. Two optional toggles go further: they create the working branches, and request a Developer sandbox for each non-production environment (sf org create sandbox --async) as the files are generated.
Choose how cautious the pipeline should be: the source directory (default force-app), check-only validation on feature branches, and whether Apex tests run after every release with an automatic rollback if they fail. The Generate CI/CD documentation toggle writes that cicd-pipeline.md team guide, saved to a folder chosen with the native VSCode picker.
A side-by-side preview of everything about to be created: files on the left, required secrets on the right. Hit Generate Files, and the pipeline YAML, shell scripts, manifests and ci-config.json land in the workspace in one click.
A panel in the editor shows the pipeline at a glance: the platform it runs on, every configured environment, the secret names needed, and whether each generated file is present. It reads live from ci-config.json and refreshes whenever that file changes.
A + button opens a quick add-environment prompt, and the refresh icon forces a manual re-read.
Everything the wizard and the panel can do is also a command, for anyone who prefers the keyboard to clicking through the UI.
| Command | What it does |
|---|---|
| SF CICD: Initialize New Pipeline | Opens the 4-step setup wizard |
| SF CICD: Add Environment | Quick prompt to add an environment to an existing config |
| SF CICD: Remove Environment | Right-click an environment in the panel to remove it |
| 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 the config is valid and all files exist |
| SF CICD: Show Secrets Checklist | List the CI secret names needed for the configured environments |
Shipped in steady, working increments: from the first release through automatic branch and sandbox creation, to a generator that writes the team's own CI/CD documentation alongside the pipeline itself.
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.
Dev added as the default first environment; feature branches now validate check-only against Dev rather than a scratch org, so every PR is proven against the real target before merge. 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: 4-step wizard, activity bar panel, ci-config.json IntelliSense, validate configuration, secrets checklist, and a getting-started walkthrough.