sf-metadata-management

You can deploy Salesforce metadata by using manifest-based retrievals and source-tracking workflows to fetch components, preview changes, and push only the selected updates to the target org safely.

Salesforce DX source format and Metadata API format differ in structure, and converting between them ensures accurate deployments and prevents unexpected org changes when retrieving or deploying components.

You can configure .forceignore to exclude specific files and components from source-tracking and deployment operations, applying ignore-conflicts semantics to avoid unintended metadata changes during CI/CD workflows.

Yes, you can retrieve specified metadata from a staging org, compare the exports with a target org, and deploy only the changed components while preserving target-only permissions like profile and permission set settings.

Using permission sets over profiles is recommended to avoid permission regressions, ensuring that target-only permissions are preserved during metadata retrieval, conversion, and deployment workflows.

Yes, sf-cli supports safe deploy previews by allowing you to run manifest-based retrievals, apply ignore-conflicts semantics, and prepare targeted deployments to reduce deployment errors before committing changes.