New Version of GitFlow-CJS v2.x series

[ChrisJStone]

Release Notes

• feat(git-flow): add support for busybox(git-flow: prefer "-f" readlink(1) option to "-e" #12)

• feat(init): add support for environment credentials (Support Git Environment Credentials #19)

Allows git flow to fall back to the same environment variables git uses
for setting the author and committer details if they are not present in
the users .gitconfig

• feat(init): add option to sign initial commit (Add option to sign the initial commit on production branch when creating a new repository with git flow init #59)

When running git flow init the following option is now available when
creating a git repository using git flow..

1. -g, --[no]sign Sign initial commit when creating a repository

When setting up git flow in a freshly created git repository with no
prior commits or when using git flow to create a git repository in an
existing folder the sign flag will create a signed empty commit with the
message initial commit.

• feat(feature): add feature release command (feat(feature): add feature release command #64)

Added git flow feature release to provide a quick way to create a
release branch from a existing feature branch.

• fix(hotfix): git flow hotfix track fails due to branch name check (fix: git flow hotfix track fails due to branch name check #68)
• feat(hotfix): add cherrypick option to hotfix finish (feat: add cherrypick option to hotfix finish #73)
• feat(hotfix): add backmerge option to release branch (feat(hotfix): add backmerge option to release branch #71)
• fix(hotfix): git flow hotfix finish -b back-merges to develop (fix: git flow hotfix finish -b still back-merges to develop #66)

When runing hotfix finish the following options have been the following
options have been added:

1. -r, --releaseBackmerge Back-merge to release branch if exists
2. -c, --cherrypick Cherry Pick to develop instead of merge
3. -b, --[no]nobackmerge Don't merge master, or tag onto develop

NOTE: One one of the above three options can be used at any given time
since it doesn't make sence to combine them.

• fix(log): fix git flow log help message (<fix>(git-flow-log): fixed help message #15)

git flow log help no longer implies it can only be used with feature
branches