"git flow release finish foo" fails with "fatal: no tag message?"

[Curious Yogurt]

I am getting the following message when issuing "git flow release
finish foo":

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

Here is the sequence of steps to reproduce, with a brand new git
repository and a single file:

touch test.txt
git init
git add .
git commit -m "Initial commit"
git flow init
[defaults accepted]
git flow release start 1.0
echo "Line 1" >> test.txt
git add .
git commit -am "Line added"
git flow release finish '1.0'

At this point, error message above pops up, and Vim is called up to
add a tag. When I add the tag and save, I end up on the master
branch, with the release/1.0 branch still existing. Any ideas what is
going wrong? Git flow version is 0.4.1.

Thank you.

[sam...@gmail.com]

I Have the same problem and would really appreciate any help.

Thanks

[justin]

The only time I've seen this is when using a visual editor that didn't block at the command line while waiting for the file to be edited. 

Is your $EDITOR set to 'vim&' instead of vim or something? Are you using 'mate' or 'subl' as your editor?

-- justin

--
http://justinhileman.com

[Mark Derricutt]

I've seen this with "subl -nw" a few times when its the FIRST time sublime starts - does git have a timeout setting or that at a much lower level in the system?

Mark

[t.schoe...@googlemail.com]

I know it´s over 2 years later. But I´m fighting now with this problem. 

I´m on osx 10.10 using git-flow, gitx and sublimetext3.

how can this:

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

be fixed be finishing a release? The standard editor is set to vim in gitconfig.

thanks,

anatol

[t.schoe...@googlemail.com]

My fault. to stupid using vim ;( for everybody else having this problem

within vim

> press i (insert mode)
> enter text
> press escape

> type :wg and return to safe the file

it works :)

cheers,

anatol