Open whmountains opened 6 months ago
Hey !
But if someone does not use annotated tags, there is no -m
option passed to git tag
, so there is still a bug. I could change the naming of "annotation" to "tag message" to always provide a tag message with a default, that could be a sane solution.
What do you think?
What a clever solution!
A co-worker helped me realize this was due to a git option called tag.gpgSign
being enabled. Tags can only be signed with GPG when they are the annotated kind. This feature can be bypassed using the --no-sign
flag. So that adds a second option to the list of potential solutions:
--no-sign
flag when annotations are disabledI would be happy with either option. I guess it depends on which semantics make more sense to you.
I guess --no-sign
could be easier. If enabled only when annotate
is false
then it should not mess with people's workflows because, as you said, I would not work anyway without the annotation.
I'll have to verify if that is fine. Is the issue currently blocking for you? Or can you use annotated tags?
Not a blocking issue for me. I intend to stick with annotated tags so I can sign them, haha. Honestly I don't know much about git tags. If there is a situation where you definitely should use non-annotated tags, I'm not aware of it.
Hi!
Could you test with the enforce-tag-msg
branch? (If you installed mix_version globally with mix archive install you need to remove it and pull the tool as a dependency)
It should always use the annotation messages, which has a default value.
On my my system, the following command opens
EDITOR
:git tag foo
. This causesmix version
to freeze since it is waiting for the editor to close.I'm using MacOS 12.5.1, with Git version 2.41.0. I can't find any git configuration which would be forcing the use of annotated tags.
This issue merits more research. I don't know what would be the best way to fix it, but I wanted to at least document the problem for other people who may be facing something similar. It is especially confusing in combination with #2, because the tool will still try to create non-annotated tags even when you specifically set
annotated: true
. Took me a while to get to the bottom of that combo!