The setup tool. One person runs it once per project to stand up the CI/CD pipeline, instead of reading platform docs, hand-writing YAML, and tracking which secrets go where. After setup, an activity-bar panel shows the live state of the pipeline so it stays easy to maintain.
Alongside pipeline files, the wizard can generate a comprehensive cicd-pipeline.md document that details branch strategy, developer workflow, secrets management, and branch protection rules. This turns CI configuration into a reusable DevOps blueprint for your team.
GitHub Actions, Azure DevOps, GitLab CI/CD, Jenkins, or Bitbucket Pipelines. The wizard generates the right file path and syntax for whichever you choose.
Pre-filled with Dev, SIT, QA, UAT, Staging and Production. Each row maps a branch to a Salesforce org alias. The feature-branch pattern (default feature/*) validates check-only, so developers raise a pull request into dev and CI must pass before it merges. Two optional toggles: Create Git Branches pushes a branch per environment to the remote straight after generation, and Create Salesforce Sandboxes requests a Developer sandbox per non-production environment via sf org create sandbox --async.
Source directory (default force-app), check-only validation on feature branches, and whether to run Apex tests after each deploy (a test failure triggers rollback). The Generate CI/CD documentation toggle writes a cicd-pipeline.md covering branch strategy, developer workflow, secrets and branch protection. Output folder is chosen with the native VS Code picker.
A two-column preview: files to be written on the left, required secrets on the right. Hit Generate Files and all the pipeline YAML, shell scripts, manifests and ci-config.json land in the workspace.
The panel reads live from ci-config.json and refreshes when the file changes. It shows the platform, every configured environment, the secret names you need, and whether each generated file is present.
The + button opens a quick add-environment prompt. The refresh icon forces a manual re-read.
| 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 |
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 VS Code 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.