Migrating from TFS to GIT, STASH. Read there is a concept of gatekeeper who has to review the code and take a call on merging with the main branch. Looking for the best practice on what developers are supposed to do, what leads are supposed to do, what administrators roles & responsibilities etc., while using these products.
Asked
Active
Viewed 245 times
0
-
By "Stash", do you mean Atlassian Stash? – ChrisGPT was on strike Mar 06 '15 at 17:24
-
@Chris Yes i meant altassian Stash – prasanth Mar 06 '15 at 17:25
-
1What kind of project? Are you accepting 3rd party commits? Are all contributors trusted? These are all questions that influence how you'd use Git. – jessehouwing Mar 06 '15 at 18:12
-
Some scenario's are explained here: http://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows – jessehouwing Mar 06 '15 at 18:44
-
Other workflows you might want to investigate:https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow https://guides.github.com/introduction/flow/ – jessehouwing Mar 06 '15 at 20:25
1 Answers
1
In stash, you can lock down branches to specific persons(gatekeepers).
For the branches that are handled by gatekeepers, you create a pull request from your source branch and only the gatekeepers have the privilege to merge the branch.
Ideally you have a develop/master branch which is locked down to developers. Developers create feature branches and work on these feature branches. Once they are done with feature branches, they create pull requests from feature branches to develop/master branch.
In case you have a medium to large team and work on more than a single release at a time, I suggest you use gitFlow
Biswajit_86
- 3,661
- 2
- 22
- 36