Like others are saying here, the branch named "master" is always deployable. Feature branches are named after a ticket. Pull requests are across branches in th

Like others are saying here, the branch named "master" is always deployable. Feature branches are named after a ticket. Pull requests are across branches in the same repo, not across repos. (It's marginally easier to collaborate on feature branches if they're all in the same repo.) We don't (yet) do full continuous deployment, so many feature branches get grouped together before a release. Our strategy is to test* each feature independently and then merge all the tickets together to a branch named "staging". The staging branch then gets run against some extra regression/acceptance tests and whatever manual tests we may want. If they pass we merge to master, tag, and deploy. Seems fine so far. Specifics about our tests and deployment process drive the Git workflow more than anything else. *Run the test suite, test manually, whatever.