Skip CI Jobs to source control when there are no changes.
After setting up a CI job from a Salesforce sandbox to a Bitbucket repo, it looks like the CI job always runs a commit, even if there are no actual changes. It would be great to not have this happen to avoid having many commits where there are no actual changes.
21
votes

-
Rúben Nunes commented
We don't experience this behavior. If there are no changes, no commit is made
-
Stenio Viveiros commented
Our team needs this.