Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Oct 8, 2010
  1. Made a note on the apt-get installer's package name.

    This fixes issue #59.
Commits on Sep 22, 2010
  1. Add FAQ note for Windows users.

Commits on Sep 6, 2010
  1. Add another FAQ.

  2. Fix more Markdown syntax.

  3. Fix markdown links to issues.

  4. Added two FAQs.

  5. @defeated
Commits on Aug 25, 2010
  1. Add installation note on how to install getopt.

    Thanks Alexander Groß.
Commits on Aug 24, 2010
  1. Added a Flattr button to the README file.

    This has been requested by at least 10 people now, so it might be time
    for one.
Commits on Aug 20, 2010
  1. @jptoto

    Fixed link to Cygwin and msysgit

    jptoto committed with
  2. @jptoto
Commits on Aug 19, 2010
  1. Make the links manually.

    I thought Markdown did support URL recognition automatically.
Commits on Jul 22, 2010
  1. Add link to git-flow-completion project.

    Also, invite users to help out on the git-flow completion for zsh.
    Personal itch that needs some serious scratching :)
  2. Remove "important" 0.2 message.

    It disturbs the layout of the README file and nobody uses 0.1 anymore
    anyway.  At least I hope (for them).
Commits on Jul 16, 2010
  1. Fix markdown issue.

  2. Added link to Google group.

Commits on Jul 10, 2010
  1. Added Rick Osborne's super-easy gitflow installer oneliner to the pro…

    See the README file for instructions on how to use it.
Commits on Apr 4, 2010
Commits on Mar 19, 2010
  1. Strip the GIT_EXEC_PATH Makefile parameter. Replaced it by the more U…

    ``prefix''. There is no need to install git-flow inside git's libexec dir by
    default. It just needs to be *somewhere* on the PATH.
Commits on Feb 24, 2010
Commits on Feb 22, 2010
Commits on Feb 15, 2010
Commits on Feb 4, 2010
  1. Added an optional <base> argument to all start subactions.

    The only exception to the rule is git-flow-support, which has an
    explicitly required <base> argument (since we cannot deduce a sane default
    name for base).
    Furthermore, these <base> arguments are checked to refer to commits on:
    - develop (for feature, release)
    - master  (for hotfix, support)
    Removed any occurrences of optional <base> arguments in finish subactions.
    The finishing target branches are clearly defined by the model. The <base>
    argument will probably confuse users. If they want the power to merge
    those feature branches into *other* branches then develop, for example,
    they can still use the magical power of Git itself for that. Gitflow
    should not provide such support.
Commits on Jan 28, 2010
  1. Forgot list command for hotfixes.

  2. Remove double entry from README.

Commits on Jan 27, 2010
Commits on Jan 26, 2010
  1. Dynamically collect the true git exec path and only if that can not b…

    …e found, use the default. Variable GIT_EXEC_PATH remains overwritable explicitly when given as a command to 'make'.
  2. Fix markdown formatting issues.

Something went wrong with that request. Please try again.