Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

No tag message error, but I don't wish to provide one. #457

Open
emilyjt opened this issue Apr 3, 2021 · 1 comment
Open

No tag message error, but I don't wish to provide one. #457

emilyjt opened this issue Apr 3, 2021 · 1 comment

Comments

@emilyjt
Copy link

emilyjt commented Apr 3, 2021

fatal: no tag message?
Fatal: Tagging failed. Please run finish again to retry

The problem is, I don't wish to provide a tag message. I cannot find a documented way to stop this, and to allow me to proceed.

This is happening when closing a release.

@Shea690901
Copy link

If I see this correct in the code (and the usage info), you need to git flow finish --noedit ....
This way you get a default message for the tag (and the merge!!!)....
If this default message is not to your liking, you must provide another message yourself!

Excerpt from man git-tag:

If one of -a, -s, or -u <keyid> is passed, the command creates a tag object,
and requires a tag message. Unless -m <msg> or -F <file> is given, an editor
is started for the user to type in the tag message.

And the tag created is an annotated one (git tag -a ...)...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants