tag:github.com,2008:https://github.com/auvik/gitflow/releases 2011-02-14T06:45:25Z tag:github.com,2008:Repository/12814627/0.4.1 2011-02-14T06:45:25Z <p>Minor update that fixes the long-standing parsing issues with shFlags on</p> <p>several platforms.</p> nvie tag:github.com,2008:Repository/12814627/0.4 2010-10-18T20:16:22Z <p>-------------</p> <p>RELEASE NOTES <br />------------- <br />* The flag parsing issues of git-flow subcommands are solved for most <br /> platforms.</p> <p>* `git flow {feature,hotfix,release} finish` now takes a `-k` flag, to keep the <br /> branch around after finishing.</p> <p>* `git flow release finish` takes a `-n` flag, to skip tagging.</p> <p>* For consistency, `git flow {release,hotfix}` now, too, have a `publish` and <br /> `track` subcommand, just like `feature`.</p> <p>* Various minor fixes.</p> nvie tag:github.com,2008:Repository/12814627/0.3 2010-07-22T14:20:37Z <p>Release 0.3</p> <p>------------- <br />RELEASE NOTES <br />------------- <br />* New subcommands for `git flow feature`: <br /> - **checkout**: <br /> For easily checking out features by their short name. Even allows <br /> unique prefixes as arguments (see below).</p> <p> - **pull**: <br /> This subcommand allows you to painlessly work on a feature branch <br /> together with another peer. This is especially valuable for doing <br /> peer reviews of other people's code. For more detailed info, see the <br /> [commit log][1].</p> <p>* Easier addressing of branch names by using name prefixes. <br /> For example, when using:</p> <p> git flow feature finish fo</p> <p> this automatically finishes the feature branch `foobar` if that's the only <br /> feature branch name starting with `fo`.</p> <p>* No force flag anymore for new feature branches <br /> `git flow feature start` lost its `-f` (force) flag. You now don't <br /> have to be in a clean repo anymore to start a new feature branch. This <br /> avoids the manual `git stash`, `git flow feature start`, `git stash <br /> pop` cycle.</p> <p>* You can use `git-flow` in stand-alone repo's now. <br /> This means it does not assume you have an `origin` repository. <br /> (Thanks [Mark][2].)</p> <p>* No commands fetch from `origin` by default anymore. <br /> There were some issues related to disabling this flag on some platforms.</p> <p>* Init guesses branch names you may want to use for `develop` and `master`.</p> <p>* Added super-easy installation script. (Thanks [Rick][3].)</p> <p>* Added BSD license.</p> <p>[1]: <a href="http://github.com/nvie/gitflow/commit/f68d405cc3a11e9df3671f567658a6ab6ed8e0a1">http://github.com/nvie/gitflow/commit/f68d405cc3a11e9df3671f567658a6ab6ed8e0a1</a> <br />[2]: <a href="http://github.com/talios">http://github.com/talios</a> <br />[3]: <a href="http://github.com/rickosborne">http://github.com/rickosborne</a></p> nvie tag:github.com,2008:Repository/12814627/0.2.1 2010-03-19T18:37:04Z <p>Release 0.2.1 -- Hotfix release to provide better (i.e. more Unix-like)</p> <p>installer options.</p> nvie tag:github.com,2008:Repository/12814627/0.2 2010-02-24T00:58:17Z <p>Release 0.2</p> <p>This is the first serious (yet still early) release that can be used in <br />production environments.</p> <p>But this is no excuse not to be careful anyway!</p> nvie tag:github.com,2008:Repository/12814627/0.1 2010-02-06T13:00:59Z <p>Release 0.1</p> <p>This is a very early (even premature) release to enthuse the open source <br />community for gitflow.</p> nvie