Repository navigation
Feature Request: Option To Automatically Update Major and Minor Version Tags #23
Description
Activity
You would like this action to offer
v1,v2, etc. Or for this action to create 2 tags? one with thex.y.zand another with justx? for the later I think we need 2 changes:in commitizen
add to the
cz versiona flag to get the different chunks, likecz version --project --format 'v$MAJOR'in commitizen-action
add a flag "major_tag" which would execute:
if [[ $INPUT_MAJOR_TAG == 'true' ]]; then git tag $(cz version --project --format 'v$MAJOR') fi
I'm open to this feature, but I don't have the capacity to add the flag to commitizen, PRs are welcome
2 tags (or 3 if we also include minor version) would be in keeping with GitHub Actions' guidance. I think it's okay to leave this open in case someone is interested in working on it eventually.
Triage: feature request — auto-update floating
vXandvX.Ytags so users can pin to e.g.commitizen-tools/commitizen-action@v0and get patch/minor updates.Out of scope for the bug/doc sweep I'm doing today; leaving for maintainer review.
Note that this repo itself already does this via the
ci/publish-major-minor-tagworkflow added in #88, so users can already pin tocommitizen-tools/commitizen-action@0or@0.27. The remaining ask is to also expose this behaviour as an opt-in input for users' own bump jobs.
release-please-action's documentation describes how one can hand-roll an approach to automatically keeping
vXandvX.Y(or simplyXandX.Yin keeping with Commitizen's existing style) tags up to date with the latest corresponding patch version. GitHub Action's own official documentation recommends such a tagging procedure: "Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work." It would be super convenient to offer an input that just does this automatically. Not sure if this issue would be better suited to the commitizen repo or here.