Add hooks to run shell snippets around git operations

[stefanzweifel]

Adds eight optional hook inputs that run inline shell snippets around each git operation the action performs (add, commit, tag, push).

Closes the long-standing ask for a generic extension point — e.g.
git fetch --unshallow before a shallow-clone commit (#365) and gives users of this Action more power.

Hooks

Hook	Runs
before_add_hook / after_add_hook	around git add
before_commit_hook / after_commit_hook	around git commit
before_tag_hook / after_tag_hook	around git tag (only when a tag is being created)
before_push_hook / after_push_hook	around git push (skipped when skip_push: true)

Each hook is an inline shell snippet evaluated in the same bash process as the action, so it sees the same INPUT_* env vars and runs in the repository's working directory. A non-zero exit aborts the action
(consistent with the existing set -eu); users can append || true to ignore a failure. Hooks only fire when their underlying step actually runs — e.g. before_add_hook is skipped on a clean tree.

Example

- uses: stefanzweifel/git-auto-commit-action@v7
  with:
    before_add_hook: git fetch --unshallow

Or multi-line via YAML's |:

- uses: stefanzweifel/git-auto-commit-action@v7
  with:
    before_commit_hook: |
      echo "About to commit at $(date)"
      ./scripts/prepare-commit.sh

See the new Hooks section in README.md for full docs.

[ro0NL]

Nice. I think we solved concurrency issues using before_push_hook

error: failed to push some refs
hint: Updates were rejected because the tip of your current branch is behind

fix:

before_push_hook: git -c user.name="${INPUT_COMMIT_USER_NAME}" -c user.email="${INPUT_COMMIT_USER_EMAIL}" pull --rebase