Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Feb 14, 2011
  1. @nvie
Commits on Feb 6, 2011
  1. @nvie

    Rewrite Joseph Levin's solution a bit.

    nvie committed
    Thanks Joseph! I've added you to the AUTHORS file, too.
Commits on Jul 9, 2010
  1. @nvie
Commits on Apr 4, 2010
  1. @nvie
Commits on Mar 25, 2010
  1. @nvie
Commits on Mar 23, 2010
  1. @nvie
  2. @nvie
Commits on Feb 24, 2010
  1. @nvie
Commits on Feb 22, 2010
  1. @nvie

    Better naming of common functions categorizing them into common,

    nvie committed
    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
Commits on Feb 21, 2010
  1. @nvie

    Check whether this is a freshly git init'ed repo that's still HEADles…

    nvie committed
    …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.
Commits on Feb 20, 2010
  1. @nvie

    Add function gitflow_has_prefixes_configured(), to check whether a re…

    nvie committed
    …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.)
  2. @nvie

    Allow for setting back a prefix to '' (empty string) by entering '-'

    nvie committed
    (dash), since the empty string '' means "take the default suggestion"
    already. Only needed in rare cases.
  3. @nvie
  4. @nvie
  5. @nvie

    Provided a better way of checking whether master/develop branches need

    nvie committed
    initialization and a more user-friendly (and more comprehensable) way of
    asking the user which branches are the master/develop branch.
  6. @nvie

    Always set the gitflow.branch.master and gitflow.branch.develop prope…

    nvie committed
    They are required. Their existence tells us that this repository is
    Added some TODO notes to implement.
  7. @nvie

    Added implementation of git-flow-init that asks the user interactivel…

    nvie committed
    …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.
Commits on Feb 15, 2010
  1. @nvie

    Fixed a problem with redirection of stdout/stderr. The specifier '2>&1'

    nvie committed
    should come *after* the redirection of stdout to /dev/null. For an
    explanation and a simple demonstration of the differences, see:

Commits on Feb 9, 2010
  1. @nvie
Commits on Jan 29, 2010
  1. @nvie
Commits on Jan 28, 2010
  1. @nvie

    Give all subcommands an optional setup() function that will be called…

    nvie committed
    … 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
Commits on Jan 27, 2010
  1. @nvie

    Refactored the subcommand invocation logic to form a more hierarchica…

    nvie committed
    …l structure and a cleaner design.
Something went wrong with that request. Please try again.