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.