Do nothing if there is nothing to do!

This isn't just an efficiency/neatness change - if you try to `git
commit` when there's nothing to commit, the command will return `1`
which will be parsed as an error, and thus the whole build will be
categorized as a failure.
This commit is contained in:
Jack Jackson 2022-11-22 11:43:31 -08:00
parent 5487859538
commit d5df1316f8

View File

@ -12,11 +12,15 @@ mkdir /working
cd /working
git clone -b "$PLUGIN_BRANCH" "$PLUGIN_GIT_REPO" .
echo "$PLUGIN_IMAGE_TAG" > "$PLUGIN_DESTINATION_FILE"
if [ "$(git status --porcelain | wc -l)" -eq 0 ]; then
echo "Nothing has changed in this repo. Nothing to do"
return
fi
git add "$PLUGIN_DESTINATION_FILE"
git config user.email "$PLUGIN_AUTHOR_EMAIL"
git config user.name "$PLUGIN_AUTHOR_NAME"
# https://stackoverflow.com/a/31926346/1040915
git commit -m "$(echo $PLUGIN_COMMIT_MESSAGE | envsubst)"
git commit -m '$(echo "$PLUGIN_COMMIT_MESSAGE" | envsubst)'
# https://stackoverflow.com/a/6174447/1040915
git remote add origin-with-credentials "$(echo $PLUGIN_GIT_REPO | sed -e's,^\(.*://\).*,\1,g')""$PLUGIN_ACCESS_TOKEN@""$(echo $PLUGIN_GIT_REPO | sed -e's,^.*://\(.*\),\1,g')"
git push origin-with-credentials "$PLUGIN_BRANCH":"$PLUGIN_BRANCH"