CI/CD Integration

sfdt is built to run unattended. When stdin is not a TTY, commands run non-interactively — confirmation prompts are skipped and the command exits with an appropriate code.

Non-interactive mode

• When stdin isn’t a TTY, sfdt skips confirm prompts and proceeds with safe defaults.
• The VS Code extension and other automated callers set SFDT_NON_INTERACTIVE=true so the CLI never hangs waiting for input.
• Destructive data operations require an explicit flag non-interactively (e.g. sfdt data delete <set> --yes).

Exit codes

All sfdt commands exit 0 on success and 1 on failure. Gate subsequent steps with set -e or by checking $?. sfdt changelog check exits 1 when the changelog needs updating, so it works as a pre-merge gate.

JSON output

Most operational commands accept --json for machine-readable output — audit, monitor, drift, rollback, doctor, extension status, and others. Pipe it into jq for assertions.

GitHub Actions

- name: Preflight and deploy
  run: |
    sfdt preflight
    sfdt test
    sfdt deploy --skip-preflight
  env:
    SFDX_AUTH_URL: ${{ secrets.SFDX_AUTH_URL }}

Explain failures automatically:

- name: Explain failure
  if: failure()
  run: sfdt explain --latest

Docker

For a self-contained toolchain (Node + sf CLI + git/jq/bash), run sfdt from the official Docker image — see Docker.