Support for creating a tag for a specific commit

[dominickgallo]

I would like to use the commit-and-tag-version tool but define a specific commit for which the tag should be created, the current code of the script lib/lifecycles/tag.js looks like this use case is not supported and the git tag is always created for the latest commit.

Could a new flag/option (e.g. --commit) be added to pass a specific commit for which the tag is created?

[TimothyJones]

This feature sounds reasonable to me, if it’s easy to achieve with the underlying libraries

…

On Wed, 9 Jul 2025 at 8:17 pm, dominickgallo ***@***.***> wrote: I would like to use the commit-and-tag-version tool but specify a specific commit for which the tag should be created for, the current code of the script lib/lifecycles/tag.js looks like this use case is not supported and the git tag is always created for the latest commit. Could a new flag/option (--commit) be added that can be passed in order to create a tag for a specific commit? — Reply to this email directly, view it on GitHub <#235>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG7HQJDLODKNYGOIOMRMO33HTT3DAVCNFSM6AAAAACBDVNW6KVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGU2TQNZWGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[dominickgallo]

Thank you for your quick response. It seems easy to achieve, if a commit sha is added to the git tag command (e.g. git tag newVersion 123a45b6) the tag would be created for the commit 123a45b6. So if a commit sha is passed via a new optional flag --commit the tag is created for that commit and otherwise for the latest commit.

Should I create an Issue for a feature request? Or create a pull request as draft?