Check for new commit before trying to push

Author: leigholiver

README.md

@@ -7,7 +7,7 @@ Action to commit a file/directory to another repo using a deploy key.
 * Add the private key to your source repo as a secret
 
 ```yaml
-uses: leigholiver/commit-with-deploy-key@v1.0.2
+uses: leigholiver/commit-with-deploy-key@v1.1.0
 with:
   source: build_output
   destination_folder: dist

VERSION

@@ -1 +1 @@
-v1.0.3
+v1.1.0

entrypoint.sh

@@ -42,10 +42,18 @@ elif [ -d $CALLING_DIR/$INPUT_SOURCE ]; then
     cp -a $CALLING_DIR/$INPUT_SOURCE/* .
 fi
 
-# commit and push
+# create the commit
 git add .
 git commit -m "${INPUT_COMMIT_MESSAGE}"
-GIT_SSH_COMMAND=$GIT_SSH git push -u origin $INPUT_DESTINATION_BRANCH
+
+# if there is a new commit - push it to the destination
+if [ ! -z "$(git cherry -v)" ]; then
+    GIT_SSH_COMMAND=$GIT_SSH git push -u origin $INPUT_DESTINATION_BRANCH
+
+# otherwise, don't try to push - this causes the workflow to fail
+else
+    echo "Nothing waiting to be pushed"
+fi
 
 # output the commit hash
 echo "::set-output name=commit_hash::$(git rev-parse HEAD)"