🔗 GitHub Flow – Scott Chacon
GitHub Flow – Scott Chacon So, what is GitHub Flow? Anything in the master branch is deployable To work on something new, create a descriptively named branch off of master (ie: new-oauth2-scopes ) Commit to that branch locally and regularly push your work to the same named branch on the server When you need feedback or help, or you think the branch is ready for merging, open a pull request After someone else has reviewed and signed off on the feature, you can merge it into master Once it is merged and pushed to ‘master’, you can and should deploy immediately For teams that have to do formal releases on a longer term interval (a few weeks to a few months between releases), and be able to do hot-fixes and maintenance branches and other things that arise from shipping so infrequently, git-flow makes sense and I would highly advocate it’s use....