A cheatsheet on the usage of git flow
HTML CSS
Latest commit 422fc9f Jul 6, 2016 @danielkummer committed on GitHub Merge pull request #59 from jlvaquero/gh-pages
Minor spanish corrections. Thanks to @jlvaquero :)
Permalink
Failed to load latest commit information.
css Adding catalan translation Dec 1, 2014
files add commands image Sep 7, 2012
img add commands image Sep 7, 2012
.gitignore Improved .gitignore file Feb 10, 2016
README.md fix with markdown syntax Mar 14, 2013
index.ca_CA.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.de_DE.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.el_GR.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.es_ES.html -Follow spanish version of Pro Git book naming convention. Jul 1, 2016
index.fr_FR.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.hr_HR.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.html Merge pull request #54 from zalari/gh-pages Apr 21, 2016
index.it_IT.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.ja_JP.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.ko_KR.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.nl_NL.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.pl_PL.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.pt_BR.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.ro_RO.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.ru_RU.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.tr_TR.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.uk_UK.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.vi_VN.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016
index.zh_CN.html Update index.zh_CN.html May 4, 2016
index.zh_TW.html replace git-flow with git-flow-avh and adjust instructions accordingly Apr 20, 2016

README.md

git-flow-cheatsheet

A cheatsheet on the usage of git flow, visit http://danielkummer.github.com/git-flow-cheatsheet/

GIT FLOW

Git extensions to provide high-level repository operations for Vincent Driessen's branching model. Read more

INIT:

$ git flow init

TRACK DEVELOP REMOTELY ON GITHUB:

$ git push origin develop

FEATURES:

Use to develop new features starting from the develop branch. Merge back into develop branch waiting for a reasonable amount of features to be there before declaring it a release.

$ git flow feature
$ git flow feature start <name>
$ git flow feature finish <name>
usage: git flow feature [list] [-v]
       git flow feature start [-F] <name> [<base>]
       git flow feature finish [-rFk] <name|nameprefix>
       git flow feature publish <name>
       git flow feature track <name>
       git flow feature diff [<name|nameprefix>]
       git flow feature rebase [-i] [<name|nameprefix>]
       git flow feature checkout [<name|nameprefix>]
       git flow feature pull <remote> [<name>]

RELEASES:

Use to group together latest development (features) add a few finishing touches if necessary and send to production. All last changes will merge back to master and develop so new features will start from current release.

$ git flow release
$ git flow release start <release> [<base>]
$ git flow release finish <release>
usage: git flow release [list] [-v]
       git flow release start [-F] <version>
       git flow release finish [-Fsumpk] <version>
       git flow release publish <name>
       git flow release track <name>

HOTFIXES:

Similar to releases but the hotfix branch starts off master to avoid unvoluntary send to production of unwanted features that my be present in branches. The quick fix must be used when an important bug arises in production which must be fixed and can't wait for other features to be ready. It merges back to master and develop.

$ git flow hotfix
$ git flow hotfix start <release> [<base>]
$ git flow hotfix finish <release>
usage: git flow hotfix [list] [-v]
       git flow hotfix start [-F] <version> [<base>]
       git flow hotfix finish [-Fsumpk] <version>