…ific functions, then gitflow-specific functions and finally, assertions to use in gitflow subcommands.
git specific and git-flow specific functions: gitflow_current_branch -> git_current_branch gitflow_is_branch_merged_into -> git_is_branch_merged_into gitflow_local_branch_exists -> git_local_branch_exists gitflow_local_branches -> git_local_branches gitflow_remote_branches -> git_remote_branches gitflow_require_branch -> require_branch gitflow_require_branch_absent -> require_branch_absent gitflow_require_branches_equal -> require_branches_equal gitflow_require_clean_working_tree -> require_clean_working_tree gitflow_require_git_repo -> require_git_repo gitflow_require_git_repo -> require_git_repo gitflow_require_initialized -> require_gitflow_initialized gitflow_require_initialized -> require_gitflow_initialized gitflow_require_local_branch -> require_local_branch gitflow_require_remote_branch -> require_remote_branch gitflow_require_tag_absent -> require_tag_absent gitflow_tag_exists -> git_tag_exists gitflow_test_branches_equal -> git_compare_branches gitflow_test_clean_working_tree -> git_is_clean_working_tree resolve_nameprefix -> gitflow_resolve_nameprefix
GIT_EXEC_PATH overrideable via Makefile command arguments.
…s. In that case, don't check if the working tree is clean (this yields errors in HEADless repos). This fix enabled users to use "git init && git flow init", too.
variables are all set (they need to be set explicitly once).
…po is fully initialized for use with gitflow. Add a means of only asking for the missing gitflow definitions, not all. (Of course, redefining all is always possible using the -f (--force) flag of init.)
(dash), since the empty string '' means "take the default suggestion" already. Only needed in rare cases.
initialization and a more user-friendly (and more comprehensable) way of asking the user which branches are the master/develop branch.
environment/branches. Added test for existence of local branches.
…ranch -a" returns remote branches with a "remotes/" prefix. "git branch -r" still returns branch names we are used to.
…es if the variable is set explicitly by gitflow.
…rties. They are required. Their existence tells us that this repository is gitflow-enabled. Added some TODO notes to implement.
…y what branches should be used for master and develop and then initializes the Git repo itself and/or the git-flow branches for him or her.
…ectly from git branch. Added gitflow_branch_exists() function for testing existence. Let gitflow_test_branches_equal() return with exit code 4 in case of the two branches having no common ancestor.
…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.
them live using git commands instead. This avoids git commands being issued by subcommands that do not necessarily require an existing Git repo to be initialized (i.e. git-flow init).
still exists one.
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