How I can use git flow release finish
in a manner that doesn't ask for merge commit messages? The -m
flag doesn't provide this, as I expected.
The goal of course is to be able to script this in such a way that doesn't require interaction.
How I can use git flow release finish
in a manner that doesn't ask for merge commit messages? The -m
flag doesn't provide this, as I expected.
The goal of course is to be able to script this in such a way that doesn't require interaction.
git flow
is (more or less) just a wrapper aroundgit
commands. Pop open thegit-flow-*.sh
of your choice, copy the git commands, and then mess with them. In this case, add--no-edit
togit merge
. This approach kills two birds with one stone: you can just copy these lines into your automation script.Unfortunately there's no out-of-the-box way to achieve that with the current version of git-flow.
By looking at the source code, the git command used to merge is
and there's no way to pass the
--no-edit
flag to it.A couple of things you could do:
You can set the environment variable
It won't invoke the editor for when you merge.
If you switch to my fork git-flow AVH Edition you can set this option to only work for when you use git-flow.
You can pass the
-m
flag to specify a tag message on the command line.It is still possible for the merges to have conflicts, but the tag operation will not try to open an editor for the tag message.
https://github.com/nvie/gitflow/wiki/Command-Line-Arguments#git-flow-release-finish--fsumpkn-version
I had trouble with the -m flag. However if you give a message without spaces, it worked. Must be a bug.
I don't know about
git flow
, but if it supports standard git flags, you can use the--no-edit
flag to avoid merge commit messages in an automated setting.