Branch for each developer in the GIT repository

Question

I want to move my project to GitHub from the local svn repository. Several developers work in this project. I thought that each developer should have his own branch in which they will make changes. When a manager reviews his work, he will merge it into a master branch. I do not need a separate repository for each developer, since GitHub has a limited number of private repositories.

Is that a good idea? What are the other alternatives?

Answer 1

Scott Chacon did a great job with Pro Git. Chapter 5 talks about distributed workflows, and I think the Integration-Manager workflow matches what you are describing.

Git Pro

, SVN , , . , , , github.

Unix. , , Github.

Answer 2

( ) ​​:

master
pre-prod
qa
devel

devel , QA devel QA , , QA ~ " " , .

, ( Gitosis) Git. , , "", , -, .

Github , , ( , ~ 400 ( ) )

Answer 3

, , , git "format-patch" , , , , .

"Decentralized with human gatekeeper": http://doc.bazaar.canonical.com/bzr.2.1/en/user-guide/bazaar_workflows.html ( , git)

, , , . , ​​Linux

Answer 4

Git , .

, http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html