Learn Git Branching - DEMO

GitHub.com flow · @mdo The term GitHub flow refers to how one can develop software with GitHub. It's a process that minimizes friction, enables asynchronous communication (and development), and is decently flexible. For an overview, read Understanding the GitHub Flow on GitHub Guides. Applying the GitHub flow to development of GitHub.com The Website™ builds on that, and tends to go something like this. 1. Find something to work on Issues on the github/github repository are the easiest way to find things to do. It's worth mentioning though that we sometimes jump right into code from a meatspace discussion or from a tweet. Bottom line? 2. At GitHub, almost every new contribution happens in a branch. My branch naming scheme is sometimes serious and relevant, and usually not useful in the slightest. sidebar_hit_areas and today_we_celebrate_our_independence_day are both branch names that I've recently worked on. Bottom line? Not every change happens in a branch. 3. Branches are ephemeral. Bottom line? 4. 5.