It's not matter of git, but rather the matter of your development strategy. If your apps are supposed to work within one project, then one repo is what you need, if these apps are in fact three different projects, then second idea is right.
You can always have different branches for each developer, one branch with all their work merged and one branch for only core changes (libs - > model, installed plugins, general configuration for environments) On 13 Wrz, 08:34, Darmen <ioxans...@gmail.com> wrote: > Hello everyone, > > Suppose we have a Project with three applications — A, B and C. Our > team: Jack, Susan and Martin. And one project leader — David. Each > programmer is working on their own application: > > A - Jack > B - Susan > C - Martin > > So, there is a problem with source code management. How to effectively > organize it with Git? I have several use-cases, but I'm not really > sure if they are correct and effective. Here they are: > > 1) One repo for whole project. > 2) Separates repositories for A, B and C apps (within their > appropriate directories in "apps" folder). > > I really like second idea, but I'm not if it's really effective. > > What do you thing and how would you organize such things? Any help > will be appreciated. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
