Stager's git branching strategy
At Stager we use a slightly modified/specialized version of OneFlow by Adam Ruka.
OneFlow’s basic premise is to have one eternal branch in your repository,
master, which should be in sync with what's currently running in production. All other branches are meant to be short-lived, and their main purpose is to facilitate code sharing and backup. Every new (production) release is based on the previous release.
master branch we have: