theevocater / coffee_recipes

In which we use science on hot and cold beverage creation

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Maintaining recipes in two branches

jaredonline opened this issue · comments

Now that master and gh-pages are the same thing, should we just drop the master branch? Add a README.md to the gh-pages branch that points visitors here and has contribute instructions?

http://oli.jp/2011/github-pages-workflow/ i've been reading that for ideas. I wouldn't mind keeping master and only pushing to gh-pages when changes are ready? I suppose any branch can do that.

It seems like some people drop master and set github to treat gh-pages as the 'default' branch in lieu of github supporting changing the branch used for pages

My personal opinion would be to drop the master branch, but keeping it around and doing git push -f origin master:gh-pages works fine for me too. A single branch just seems more simple.