On Github opdavies / drupalcamp-london-git-flow
By Oliver Davies / @opdavies
Initialising Git Flow...
~ $ git flow init
Creating your production and development branches.
~ $ git flow init No branches exist yet. Base branches must be created now. Branch name for production releases: [master] Branch name for "next release" development: [develop]
Initialising Git Flow...
~ $ git flow init No branches exist yet. Base branches must be created now. Branch name for production releases: [master] Branch name for "next release" development: [develop] How to name your supporting branch prefixes? Feature branches? [feature/] Release branches? [release/] Hotfix branches? [hotfix/] Support branches? [support/] Version tag prefix? []
Faster.
~ $ git flow init -d # Accepts the default branch names.
Starting your first feature branch.
~ $ git flow feature start foo* Branches from develop
Starting your first feature branch.
~ $ git flow feature start foo Switched to a new branch 'feature/foo' Summary of actions: - A new branch 'feature/foo' was created, based on 'develop' - You are now on branch 'feature/foo' Now, start committing on your feature. When done, use: git flow feature finish foo
Add and commit any changes as normal.
~ $ drush dl admin_menu ~ $ git add sites/all/modules/contrib/admin_menu ~ $ git commit -m "Added admin_menu"
Finishing a feature.
~ $ git flow feature finish foo
Finishing a feature.
~ $ git flow feature finish foo Switched to branch 'develop' Already up-to-date. Deleted branch feature/foo (was d0cadf1). Summary of actions: - The feature branch 'feature/foo' was merged into 'develop' - Feature branch 'feature/foo' has been removed - You are now on branch 'develop'
And repeat...