I don’t know if it happens to me only due to my complex source control configuration (which uses SSH keys like Github), but it happens quite often to me that the release process gets stuck right when it’s time to push changes.
When this happens you are left with almost no choice but to perform a release:rollback and start again, but today I’ve found a good solution to this problem:
So, if your release preparation process is interrupted for some reason and you want to restart it again, but when you try you get a message saying the git commit command failed, then just do the following:
git reset --soft HEAD~1
This command will remove the commit from your local clone leaving all the Maven changes intact, thus allowing you to recover the process where you left it.