Abort Capistrano 2 deployment if remote is dirty

I configured Capistrano 2 to abort deployment if remote directory is dirty.

Because uncommited changes in remote directory will cause degrade.

# Of course, modifying source code in remote directory is bad, but sometimes we need to do it.

If there are some changes in remote, deploy log would be like this:

Capistano 3

Capistrano 3 doesn’t clone repository for each releases so we can’t port this task.

I’m seeking other solution to protect remote changes from automated deployments.