git flow init.|
Feature branch
|
For developing new features
|
|
Release branch
|
Staging area for new releases
|
|
Hotfix branch
|
Production fixes (based on
master) |
|
Bugfix branch
|
Development fixes (based on
develop) |
|
Support branch
|
Production fixes for a specific release
|
|
Show feature branches
|
git flow feature [list] |
|
Start a new feature
|
git flow feature start FEATURENAME |
|
Publish feature branch to remote
|
git flow feature publish FEATURENAME |
|
Finish up a feature
|
git flow feature finish FEATURENAME |
develop.
|
Show release branches
|
git flow hotfix [list] |
|
Start a new release
|
git flow hotfix start VERSION |
|
Publish release branch to remote
|
git flow hotfix publish VERSION |
|
Finish up a release
|
git flow hotfix finish VERSION |
master and develop while also tagging it.
|
Show hotfix branches
|
git flow hotfix [list] |
|
Start a new hotfix
|
git flow hotfix start FIXNAME |
|
Publish hotfix branch to remote
|
git flow hotfix publish FIXNAME |
|
Finish up a hotfix
|
git flow hotfix finish FIXNAME |
master.
|
Show bugfix branches
|
git flow bugfix [list] |
|
Start a new bugfix
|
git flow bugfix start FIXNAME |
|
Publish bugfix branch to remote
|
git flow bugfix publish FIXNAME |
|
Finish up a bugfix
|
git flow bugfix finish FIXNAME |
develop.
|
Show support branches
|
git flow support [list] |
|
Start a new support branch
|
git flow support start VERSION |
I think you should integrate the fact to the base can be provided. For instance: git flow feature start login feature/security
Cheatography n. The art of mapping complex subjects into clear, instantly navigable reference guides.