… which gets called if subargument is not help
Signed-off-by: Vincent Driessen <firstname.lastname@example.org>
This reverts commit fff16ed.
This allows a user to create a symbolic link to git-flow in their personal bin directory (e.g. ~/bin) without having to add the source tree to their $PATH or do a system install.
…sumed existence of a valid git repo. Instead, functions gitflow_load_settings() and gitflow_require_git_repo() have been added that can be called in each submodule that requires such. Specifically, git-flow init does NOT use this.
should come *after* the redirection of stdout to /dev/null. For an explanation and a simple demonstration of the differences, see: http://is.gd/8srJR
https://wiki.ubuntu.com/DashAsBinSh Went back from making use of the specific Bourne shell construct 'typeset -i' for easy integer calculations (typeset -i foo=123; foo=foo+456;) to a more compatible way (local foo=123; foo=$((foo+456)); ) The 'typeset -f' call has been replaced by a call to 'type', effectively not testing for existence of a declared *function*, but testing for existence of a declared *something*. You have to sacrifice sometimes in order to be more portable.
Renamed shFlags.sh -> gitflow-shFlags
…s up again, the convenience functions flag() and noflag() have been used and all occurrences of 0 and 1 are replaces by true and false. This makes it safe (and more readable!) to test for active/inactive flags. Also specify $FLAGS_PARENT explicitly, to avoid having the generated usage texts by shFlags mention the full Unix path to $0, but instead use the more recognizable varient 'git flow feature'.
Now also installs the shFlags.sh script. (The license lines are included in its header.)
Implement the flags for each of the 'feature' subcommands.
…at returns error codes instead of dies. Rewrote gitflow_require_clean_working_tree() in terms of that.
…t directory. Add a function that tests whether a specific commit is already merged into the given target branch.
Conflicts: git-flow-feature git-flow-hotfix git-flow-release git-flow-support
… by git-flow in order to let the subcommand initialize its environment. Give all the branch-type subcommands a default explicit "list" action, too. Order the functions inside each of the subcommands in a specific order, for consistency: - usage() - setup() - cmd_default() - cmd_list() - cmd_help() - parse_args() - other commands
…l structure and a cleaner design.