Support for tag pushing, without files changes

[zMynxx]

Hey team,

Great action, nearly became a standard for regular pipelines usage.
However, I was wondering its possible to add a support for pushing tag when no files had changed.
For example, on my release pipeline I perform git tag (with message) and push to main, without commiting any files / changing any files at all. I tried to to the same using this action but when no files changes detected if fails with exit code 1.
Is there a change to add a feature flag for this so I can stick to using this across my pipeline as my go-to standard?

much appriciated!

[zMynxx]

Added a example use case, from [this](https://github.com/zMynx/aws-lambda-calculator/actions/runs/13704223421/job/38325595322) pipeline I'm currently working on.

[stefanzweifel]

Thank you so much for your kind words and for sharing your suggestion! ❤️

I understand where you're coming from, but I think this particular feature might be a bit outside the scope of git-auto-commit. From what I gather, what you're looking to do can be accomplished quite simply with these commands:

# Create an annotated tag
git tag -a "v1.0.0" -m "Release v1.0.0"

# Push the tag to the remote repository
git push origin "v1.0.0"

I would recommend adding these commands as a step in your workflow. It keeps things straightforward without adding extra complexity to git-auto-commit, which already has a lot of features.

Thanks again for your input, and I really appreciate your understanding! If you have any other ideas or questions, feel free to share! 😊

[zMynxx]

I use the following in order to achieve my goal, it mimic the desire use:

      - name: Git tag
        run: |
          git config --local user.name github-actions[bot]
          git config --local user.email github-actions[bot]@zmynx.users.noreply.github.com
          git tag v${{ needs.package.outputs.release_version }} -m "Release v${{ needs.package.outputs.release_version }}"
          git push origin v${{ needs.package.outputs.release_version }}

but I think this particular feature might be a bit outside the scope of git-auto-commit. From

Honestly I can't phantom why it is so out-of-scope, at the moment the git-auto-commit action hold the abilities to add files, commit, set the message, tag the commit and push all to the remote. All I'm asking is to be able to override the need to perform the git commit -a in order to push a tag without effecting files. It's just anti-pattern to allow automations / pipeline entities to add commits to the main branch of the repository.
I might just fork this to add a feature-flag commit: false, or something like that.

Thanks anyways

[stefanzweifel]

I appreciate your feedback, and I'm sorry if my previous response triggered you.

I mentioned that the feature you’re suggesting might be out of scope because the primary purpose of git-auto-commit is to create commits. Over the years, the feature set has grown, but the core intention of the action has remained the same: to create and push commits.

You want to bypass a significant portion of git-auto-commit's functionality just to create a tag and push it. I prefer to keep tools straightforward and focused, which is why I’m not inclined to add this feature at this time.

If you believe you can implement the feature you’re looking for, I encourage you to submit a pull request. I’m open to reviewing it and providing feedback.

[zMynxx]

done 😄