fix: Configure git pull to rebase instead of merge

If the branch has not been updated while the action is running, then the
pull will be a no-op either way, and the push will succeed. If the
branch has been updated since the repository was initially checked out,
then rebase rather than merge when pulling so that no merge commit will
be created. If the rebase can not be performed non-interactively, then
it will fail immediately, and there's nothing further that can be done.
Configuring pull behavior has the added benefit of eliminating a
twelve-line warning from Git about pulling without specifying how to
reconcile divergent branches.

Author: Kurt-von-Laven

entrypoint.sh

@@ -28,9 +28,10 @@ pip install "$INPUT_COMMITIZEN_VERSION" $INPUT_EXTRA_REQUIREMENTS
 echo "Commitizen version:"
 cz version
 
-echo "Configuring git user and email..."
+echo "Configuring Git username, email, and pull behavior..."
 git config --local user.name "$INPUT_GIT_NAME"
 git config --local user.email "$INPUT_GIT_EMAIL"
+git config --local pull.rebase true
 echo "Git name: $(git config --get user.name)"
 echo "Git email: $(git config --get user.email)"