You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
release-please-action's documentation describes how one can hand-roll an approach to automatically keeping vX and vX.Y (or simply X and X.Y in 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.
The text was updated successfully, but these errors were encountered:
You would like this action to offer v1, v2, etc. Or for this action to create 2 tags? one with the x.y.z and another with just x? for the later I think we need 2 changes:
in commitizen
add to the cz version a flag to get the different chunks, like cz 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.
release-please-action's documentation describes how one can hand-roll an approach to automatically keeping
vX
andvX.Y
(or simplyX
andX.Y
in 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.The text was updated successfully, but these errors were encountered: