… which gets called if subargument is not help
Signed-off-by: Stefan Naewe <email@example.com>
…check was always false - Added fetching develop branch from origin when fetch flag is on in feature finish
This patch was originally contributed as a workaround for the cases where there were flags that took the first argument position. This fix was just plain wrong and this commit reverts it.
This is useful for small projects.
Simply step aside to the master branch instead.
For example, you could set the versiontag prefix to be: git config --global gitflow.prefix.versiontag "production/\$(date +%Y/%m/%d/)" which would result in tag names like: production/2010/09/22/my-hotfix-or-feature-name NOTE: Although this is a useful addition in the current version of git-flow, in a future reimplementation of it in Python, this will be replaced by hook scripts, so be sure not to rely on this feature too much for now.
…nder the release
This already was the default behaviour of git-flow-feature, but now it is the default for the other scripts, too. RATIONALE: Due to limitations on some platforms (and some implementations of getopt), it's impossible to turn off the -f (fetch) option. Therefore, it must now be set explicitly. Also, this makes git-flow work in stand-alone repositories (i.e. repos that do not have an origin remote at all).
…rresponding branches found.