Cached Build Commands

DeployBot has a Cached Build Commands feature whereby certain commands (such as composer install or yarn install) are only run when changes are detected to certain files (such as composer.lock or yarn.lock, for example).

It would be great to have this functionality in DeployHQ too, as although we can define cached folders currently, we’re having to run composer install and yarn install for every deployment, which increases the deployment time for deployments unnecessarily if these files haven’t changed (so just the front-end build command such as yarn development or yarn production, in the case of a Laravel Mix-based build, can be run in isolation from their respective install commands).