Feature/branch prefixes as subcommands

[70853n]

How to test

• run git flow init
• when asked for delimiter enter custom delimiter (only valid characters for git branch names)
• when asked for branch prefixes, enter custom prefix (without delimiter)
• run git flow help
• run git flow <prefix> help
• run git flow <prefix> <subaction>

Example

$ git flow init
No branches exist yet. Base branches must be created now.
Branch name for production releases: [master] release
Branch name for "next release" development: [develop] integration

How to name your supporting branch prefixes?
Delimiter between prefix and name? [/] 
Feature branches? [feature] change
Release branches? [release] candidate
Hotfix branches? [hotfix] 
Support branches? [support] 
Version tag prefix? [] 

$ git flow help
usage: git flow <subcommand>

Available subcommands are:
    init    Initialize a new git repo with support for the branching model.
    change  Manage your change branches.
    candidate   Manage your candidate branches.
    hotfix  Manage your hotfix branches.
    support Manage your support branches.
    version Shows version information.

Try 'git flow <subcommand> help' for details.

[70853n]

I'm not sure whether I've overlooked some instances where the default subcommand name is not replaced, or I wasn't able to change that. Gotta look into it, some time, if anyone still cares about this project.

Example

$ git flow change start the-first-part-of-a-bigger-feature
Switched to a new branch 'change/the-first-part-of-a-bigger-feature'

Summary of actions:
- A new branch 'change/the-first-part-of-a-bigger-feature' was created, based on 'integration'
- You are now on branch 'change/the-first-part-of-a-bigger-feature'

Now, start committing on your feature. When done, use:

     git flow feature finish the-first-part-of-a-bigger-feature

Can someone think of an easy fix for that?

[ChrisJStone]

I working on updating a fork here feel free to submit an issue or pull request to see if we can get this implemented