blob: 72c04bc7f81266ef22979a13669b6896f6f3fe17 [file] [log] [blame]
Vincent Driessen2d0cbec2011-02-06 07:52:43 +010010.4.1:
2-----
Vincent Driessen4b5b9322011-02-14 07:44:18 +01003Release date: **2011/02/04**
Vincent Driessen2d0cbec2011-02-06 07:52:43 +01004
5* New option `-d` added to `git flow init`, to initialize with defaults without
Vincent Driessen4b5b9322011-02-14 07:44:18 +01006 asking for input interactively. Ideal for creating git-flow enabled repos in
7 custom scripts.
Vincent Driessen2d0cbec2011-02-06 07:52:43 +01008
9* The parsing issues related to git-flow feature's flags are now dealt with on
10 all known platforms. (Fixed #54, #62, #86, #97)
11
12* Escape queries for detecting branch/tag names. (Fixed #91)
13
14
Vincent Driessen3d41ea02010-07-22 16:16:17 +0200150.4:
16---
Vincent Driessen1c289cf2010-10-18 21:46:28 +020017Release date: **2010/10/18**
Vincent Driessen3d41ea02010-07-22 16:16:17 +020018
Vincent Driessen1c289cf2010-10-18 21:46:28 +020019* The flag parsing issues of git-flow subcommands are solved for most
20 platforms.
21
22* `git flow {feature,hotfix,release} finish` now takes a `-k` flag, to keep the
23 branch around after finishing.
24
25* `git flow release finish` takes a `-n` flag, to skip tagging.
26
27* For consistency, `git flow {release,hotfix}` now, too, have a `publish` and
28 `track` subcommand, just like `feature`.
29
30* Various minor fixes.
Vincent Driessen3d41ea02010-07-22 16:16:17 +020031
32
Vincent Driessen02548fb2010-07-22 16:12:26 +0200330.3:
34----
35Release date: **2010/07/22**
36
Vincent Driessen2da88102010-07-22 16:03:22 +020037* New subcommands for `git flow feature`:
38 - **checkout**:
39 For easily checking out features by their short name. Even allows
40 unique prefixes as arguments (see below).
41
42 - **pull**:
43 This subcommand allows you to painlessly work on a feature branch
44 together with another peer. This is especially valuable for doing
45 peer reviews of other people's code. For more detailed info, see the
46 [commit log][1].
47
48* Easier addressing of branch names by using name prefixes.
49 For example, when using:
50
Vincent Driessen02548fb2010-07-22 16:12:26 +020051 git flow feature finish fo
Vincent Driessen2da88102010-07-22 16:03:22 +020052
53 this automatically finishes the feature branch `foobar` if that's the only
54 feature branch name starting with `fo`.
55
56* No force flag anymore for new feature branches
57 `git flow feature start` lost its `-f` (force) flag. You now don't
58 have to be in a clean repo anymore to start a new feature branch. This
59 avoids the manual `git stash`, `git flow feature start`, `git stash
60 pop` cycle.
61
62* You can use `git-flow` in stand-alone repo's now.
63 This means it does not assume you have an `origin` repository.
Vincent Driessen02548fb2010-07-22 16:12:26 +020064 (Thanks [Mark][2].)
Vincent Driessen2da88102010-07-22 16:03:22 +020065
66* No commands fetch from `origin` by default anymore.
67 There were some issues related to disabling this flag on some platforms.
68
69* Init guesses branch names you may want to use for `develop` and `master`.
70
Vincent Driessen02548fb2010-07-22 16:12:26 +020071* Added super-easy installation script. (Thanks [Rick][3].)
Vincent Driessen2da88102010-07-22 16:03:22 +020072
73* Added BSD license.
74
75[1]: http://github.com/nvie/gitflow/commit/f68d405cc3a11e9df3671f567658a6ab6ed8e0a1
Vincent Driessen02548fb2010-07-22 16:12:26 +020076[2]: http://github.com/talios
77[3]: http://github.com/rickosborne
Vincent Driessen2da88102010-07-22 16:03:22 +020078
Vincent Driessen02548fb2010-07-22 16:12:26 +020079
80Older versions
81--------------
82No change history is recorded for pre-0.3 releases.