Branch for each developer in GIT repo -


I want to move my project from the local SVN repository to GitHub. Many developers are working perfectly on this project. I was thinking that every developer should have his own branch in which he will make changes. When the manager reviews his work, he will merge it into the master branch. I do not want separate stores for every developer because GitHub has a limited number of personal treasures.

Is this a good idea? What are the other options?

Scott Chacon has done a great job with Pro Git Book. Chapter 5 talks about the distributed workflow and I think the Unity-Manager workflow fits in with the work you describe.

Also remember that unlike SVN, every developer has his own repository , not just a working copy, on his development machine Investigated. Similarly, you can clone an unrivaled store on a shared server on your internal network, you can commit your developers to that repo and then drag your maintenance from internal repositories, integrate changes and then go to github .

In that workflow, you manage bare repo and control permissions on your own machine through regular UNIX user accounts. You can not be constrained by the number of developers who can push your internal repo as you would with Gitanbu.


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -