It has come to our notice that the sncicd-apply-changes action fails when the target instance has local changes to stash. When the failed pipeline is re-run, it succeeds (because the stash is already done?). The chances of target instance having local changes are high as we move code into it using update-sets for quick tests. Is there a way to enable stashing in the action to prevent it from failing?
It has come to our notice that the sncicd-apply-changes action fails when the target instance has local changes to stash. When the failed pipeline is re-run, it succeeds (because the stash is already done?). The chances of target instance having local changes are high as we move code into it using update-sets for quick tests. Is there a way to enable stashing in the action to prevent it from failing?
Thanks Ramya