Indeed, the title says it all.

A detailed walk through of one way to manage a development and release process using branches with git. Clean, plenty of example command, and a PDF summary diagram for printing.

A nice post on different git workflows. The best part is about branch naming: "Using ‘origin’ as the name of your remote and ‘master’ as the name of your main branch is just the default settings git gives you. Neither name is magic. So, I renamed ‘origin’ to ‘github’ in .git/config to be explicit about where the code is going. Then, I created a new branch ‘development’ to reflect the code that is under the mainline of development."