Release tag message flag about gitflow HOT 16 OPEN

Closing this, as this has the same cause (under the hood) as issue #28.

from gitflow.

I no longer get the fatal flag message but now if I use the -m flag it ignores it and opens the default editor.

git flow release finish '0.1.0' -m 'Testing a release'

Using Ubuntu 10.10 with latest develop branch

from gitflow.

Yeah, the flags should come before the arguments, Unix style. This is an shFlags limitation, I'm afraid.

It might be a an option to error on superfluous arguments (as the -m and the message are treated), but this leads to a whole lot of other issues, I'm afraid. Best for now to stick to good old Unix habits.. :(

Cheers,
Vincent

from gitflow.

Interesting, I hadn't made that connection before with the flags.

I tried this:

git flow release finish -m 'Testing tagging' '0.1.0'

But I get this error now:

fatal: Failed to resolve '0.1.0' as a valid ref.
Tagging failed. Please run finish again to retry.

Running git branch:

  develop
  master
* release/0.1.0

Running the command without the -m flag still works.

from gitflow.

Hmm. I've tested things here on my Mac, but the only thing I get is this:

flags:FATAL the available getopt does not support spaces in options

on the space in the quoted -m flag value, which scares me even more :)

What OS are you running?

from gitflow.

I'm using Ubuntu 10.10 with the latest from the develop branch.

from gitflow.

Is this related? I'm seeing this on OS X:

➜  ~rvm_rvmrc_cwd git:(hotfix/fix_loc_search_500_on_staging_and_prod) ✗ git flow hotfix finish fix_loc_search_500_on_staging_and_prod
Switched to branch 'master'
Merge made by recursive.
 app/controllers/api/locations_controller.rb |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
fatal: no tag message?
Tagging failed. Please run finish again to retry. 

from gitflow.

I'm having the same behavior of elight. Right now I have to use git commands to merge and tag, because it do not work.

from gitflow.

also come cross this msg occur:

xds2000@localhost demo$ git flow release finish 'v0.1.0' -m 'Testing a release'
fatal: no tag message?
Tagging failed. Please run finish again to retry.

from gitflow.

@xiaods: Yeah, like said, you should use the -m flag before the branch name, UNIX style.

from gitflow.

@nvie, i have review this thread list, see our's comments. i suggesting print some hits on it?

from gitflow.

@nvie can you pull these changes? They work for me.
Thanks @Zoramite, I can now do: git flow release finish -m "$MSG" $REL

from gitflow.

Hi,

This issue is really bugging me and seems to be fixed yet when I pull from git hub the latest changes seem to be Dec 06 2011? So I assume I've not got the fix discussed above done in late december ...

Has the github respository not been updated? Or am I doing something wrong to get the latest version?

Ta.

from gitflow.

It has not been updated since Dec 06 2011

from gitflow.

I applied the fix myself, since its just two lines to edit: https://github.com/nvie/gitflow/pull/160/files

• or you could just use @Zoramite's fork.

Perhaps @nvie is otherwise engaged, there do seem to be a large number of forks for Gitflow.

from gitflow.

Thanks, that's great, I'll apply the fix myself.

from gitflow.