-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tag message for annotated_tag option #558
Comments
Hi @frerksaxen , thanks for the feedback. I'm afraid I did not get the point. Could you please add some examples so that we could take a look? |
@Lee-W Sure. I changed the original Description. Hope it's much clearer now. |
I agree with the idea of adding a message apart from the tag_name |
Hi, I'm good with the high-level idea. But might need some more discussion on how the detail would be implemented |
Sounds great! I'll take a deeper look when I have time. Thanks! |
FWIW you can look in this page how that'd look in Gitlab: https://gitlab.gnome.org/GNOME/geary/-/tags Annotated screenshot about annotated tags: |
any updates? |
Description
Currently, with
cz bump --annotated-tag
, a tag will be created with the tag message being like the tag itself, just the new version. It's basicallygit tag -a -m <version> <version>
.However, git provides the possibility of adding elaborate messages to the annotated tag:
git tag -a -m <message> <version>
.It would be great if we could add custom tag messages that could include:
Possible Solution
Maybe adding custom messages:
cz bump --annotated-tag-msg "This new version will improve your life."
Maybe adding the changelog:
cz bump --annotated-tag-changelog
Maybe adding author and date:
cz bump --annotated-tag-credentials
And maybe everything combined:
cz bump --annotated-tag-msg "This new version will improve your life." --annotated-tag-changelog --annotated-tag-credentials
might result in the git tag:
2.32.0
with the tag message:
Additional context
No response
Additional context
This is related to the following pull request: #272
The text was updated successfully, but these errors were encountered: