Skip to content
This repository
November 16, 2013
August 12, 2013
August 11, 2013
May 31, 2013
April 27, 2013
March 15, 2013
February 25, 2013
January 22, 2013
January 22, 2013
January 21, 2013
November 13, 2012
November 13, 2012
October 14, 2012
October 11, 2012
July 27, 2012
June 10, 2012

1.0.0-avh

Tagged 1.0-avh
First official release of the AVH version of git-flow
May 31, 2012

0.4.2-avh2

Remove the submodule shFlags.
Instead of the submodule we'll just use the file.
February 13, 2011

0.4.1

Minor update that fixes the long-standing parsing issues with shFlags on
several platforms.
October 18, 2010

0.4

-------------
RELEASE NOTES
-------------
* The flag parsing issues of git-flow subcommands are solved for most
  platforms.

* `git flow {feature,hotfix,release} finish` now takes a `-k` flag, to keep the
  branch around after finishing.

* `git flow release finish` takes a `-n` flag, to skip tagging.

* For consistency, `git flow {release,hotfix}` now, too, have a `publish` and
  `track` subcommand, just like `feature`.

* Various minor fixes.
July 22, 2010

0.3

Release 0.3
-------------
RELEASE NOTES
-------------
* New subcommands for `git flow feature`:
  - **checkout**:
    For easily checking out features by their short name.  Even allows
    unique prefixes as arguments (see below).

  - **pull**:
    This subcommand allows you to painlessly work on a feature branch
    together with another peer.  This is especially valuable for doing
    peer reviews of other people's code.  For more detailed info, see the
    [commit log][1].

* Easier addressing of branch names by using name prefixes.
  For example, when using:

  	git flow feature finish fo

  this automatically finishes the feature branch `foobar` if that's the only
  feature branch name starting with `fo`.

* No force flag anymore for new feature branches
  `git flow feature start` lost its `-f` (force) flag.  You now don't
  have to be in a clean repo anymore to start a new feature branch. This
  avoids the manual `git stash`, `git flow feature start`, `git stash
  pop` cycle.

* You can use `git-flow` in stand-alone repo's now.
  This means it does not assume you have an `origin` repository.
  (Thanks [Mark][2].)

* No commands fetch from `origin` by default anymore.
  There were some issues related to disabling this flag on some platforms.

* Init guesses branch names you may want to use for `develop` and `master`.

* Added super-easy installation script. (Thanks [Rick][3].)

* Added BSD license.

[1]: http://github.com/nvie/gitflow/commit/f68d405cc3a11e9df3671f567658a6ab6ed8e0a1
[2]: http://github.com/talios
[3]: http://github.com/rickosborne
March 19, 2010

0.2.1

Release 0.2.1 -- Hotfix release to provide better (i.e. more Unix-like)
installer options.
February 23, 2010

0.2

Release 0.2
This is the first serious (yet still early) release that can be used in
production environments.

But this is no excuse not to be careful anyway!
February 06, 2010

0.1

Release 0.1
This is a very early (even premature) release to enthuse the open source
community for gitflow.
Something went wrong with that request. Please try again.