When removing/renaming components after previous deployments, the old component folders in deployment/work are not deleted. This is intended behaviour but can oftentimes lead to forgotten code on the remote.
Would it be possible to implement a routine on the remote side that warns at deploy time about untracked component folders so that the user can then decide whether or not to remove them?
When removing/renaming components after previous deployments, the old component folders in deployment/work are not deleted. This is intended behaviour but can oftentimes lead to forgotten code on the remote.
Would it be possible to implement a routine on the remote side that warns at deploy time about untracked component folders so that the user can then decide whether or not to remove them?