Sandbox Deployment With 0 Components
Running a deployment into a Sandbox or Prod that has 0 components is a waste of time and resources.
If a deployment has 0 components in it, either
1. There's a problem because I was expecting greater than zero (so throw an error), or...
2. I want to run tests, and theres a different command for that (I shouldn't be executing a deployment just to run tests).
Justin Lyon
shared this idea
-
Gearset has already done the hard work of identifying that there are 0 component changes to be deployed. So under this scenario it should just NOT deploy into the target if that target is a sandbox or prod.
This happens most commonly when I am making updates to keep the repository in sync with the sandboxes, but the sandboxes already have the changes. Or if I'm making maintenance updates on our git repo that have no Salesforce components in them.