@terminon
github.com/bloveridge
~40 bytes
1. http://nvie.com/posts/a-successful-git-branching-model/
2. http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/
1. https://guides.github.com/introduction/flow/
2. http://scottchacon.com/2011/08/31/github-flow.html
"development"
"production"
$ git checkout -b feature/cart development
$ git commit
$ # rinse and repeat
$ git checkout development
$ git merge --no-ff feature/cart
$ # cleanup
$ git branch -d feature/cart
$ git flow feature start cart
$ git commit
$ # rinse and repeat
$ git flow feature finish cart
$ git flow release start 4.2.2
$ vim package.json # update version in package file
$ git commit
$ git flow release finish 4.2.2
$ git checkout -b rel/4.2.2 development
$ vim package.json # update version in package file
$ git commit
$ git checkout production
$ git merge --no-ff rel/4.2.2
$ git checkout development
$ git merge --no-ff 4.2.2
$ git tag -a 4.2.2
$ git flow hotfix start 4.2.3
$ git commit # fix bug
$ vim package.json && git commit # update version in package file
$ git flow hotfix finish 4.2.3
$ git checkout -b hotfix/4.2.3 production
$ git commit # fix bug
$ git commit # update version in package file
$ git checkout production
$ git merge --no-ff hotfix/4.2.3
$ git checkout development
$ git merge --no-ff 4.2.3
$ git tag -a 4.2.3
$ git flow support start 1.8.6 1.8.5
$ git commit # fix bug
$ git commit # fix more bugs
$ git tag -a 1.8.6 # tag if you want to, but don't merge it
$ git checkout -b support/1.8.6 1.8.5
$ git commit # fix bug
$ git commit # fix more bugs
$ git tag -a 1.8.6 # tag if you want to, but don't merge it
https://guides.github.com/introduction/flow/
http://scottchacon.com/2011/08/31/github-flow.html
http://nvie.com/posts/a-successful-git-branching-model/
http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/
https://github.com/petervanderdoes/gitflow