How BizeeBee uses Github to build BizeeBee

For more details or to answer your own questions, please see the following resources first:

http://progit.org
http://zachholman.com/talk/how-github-uses-github-to-build-github

Transcript

1. how uses to build thanks @holman for the inspiration over at http://zachholman.com/talk/how-github-uses-github-to-build-github
2. The Goal: Release Often • Pull requests are the workflow • needs code review • has been merged into master and pushed to demo • should be pushed to production in the next release • has been pushed to production
3. The Lowdown org/master topic branch in a fork of one of the repos topic branch in a fork of one of the repos topic branch in a fork of one of the repos pull request pull request pull request demo production
4. org/master • This repo contains the latest version of code that is currently on demo (and/or production) for that project • You may find out what features are in what state by looking at the pull requests
5. Topic Branches • Are created by developers in their forks • Are branched off master • Grouping of functionality written for a feature, bug, or chore • Grouping of functionality for experimentation • May be used as a basis for pull requests • Should not have functionality outside of the “topic” for which the branch was created
6. Pull Requests • They are effectively a code review tool • Should have the story id # (from Pivotal tracker) and the topic branch/ feature name in its title • Should be labeled as review, demo, release-ready or in-production • Should be used for discussion about implementation details • Started from topic branches • May be merged by developers other than the ones that created them • All test suites must be green before a pull request is merged into master (the exception are examples that are known to fail) • Bugs found on demo reopen the associated pull request