CI/CD sfdx deployments using Saleforce CLI by default deploys all the metadata into the Orgs.
Is this recommended ? Or should we limit the deployments to changed components alone (using package.xml)?
If we have to limit the deployment using package.xml, what is the best approach/tools to generate the package.xml and destructiveChanges.xml files in an automated manner. Or, is this the responsibility of the developer to modify these files and check-in to repository.
2 answers
Hi @Jenin James
I started using a scolladon/sfdx-git-delta: Generate the sfdx content in source format from two git commits (github.com)
For incremental deployments its fit for me
