How to structure multiple projects in Git

Question

At the company where I work, we use Visual Studio 2013 and TFVC for versioning the projects.

I’m used to the Source Control Explorer, be able to give Get Latest Version at any level (the entire repository, a group of projects, just a project or a specific file), create Branch and clearly see the "folder" created with the new branch, etc.

The structure of the projects was organized as follows:

- Repositório
  -- Grupo_de_Projetos_1
     --- Projeto_1
         ---- Development
              ----- Source
                    ...
         ---- Main
              ----- Source
                    ...
         ---- Release
              ----- Source
                    ...
      --- Projeto_2
          ...
      --- Projeto_3
          ...

  -- Grupo_de_Projetos_2
    --- Projeto1
        ...

Basically with this structure it was possible to authorize access to the entire repository, to a group of projects or even to just one specific project. Each project was organized in 3 Branchs (Development, Main and Release), all just an exact copy. So the developers worked on Development and then we could do the Merge in Main to then send to Release. So when a bug in production, we resolve directly in Release, we publish and then replicate the correction for others Branchs, and the game follows.

Now it’s been decided to move to Git, and I’ve been responsible for the migration, but I’m having trouble putting together the folder structure (I can already understand the commands and many concepts used).

Looking at my old structure on TFVC, would it be possible to create something similar? (I know that the Branchs will no longer be seen in the same way).

Let’s go to Checklist:

1. I already have my repository created, so it would be equivalent to my first level of the structure shown earlier (-)?
2. Would my Group_de_projects_1 (-) be a "subrepository" or simply a folder? It would be possible to configure access levels to a folder?
3. Each (---) project would be a "subrepository" as well, in order to create the Branchs or simply a folder? It is possible to create a folder Branch only for a folder?

I saw a little bit about submodule, would perhaps be an option in this context?

I was also in love with this tip from Microsoft, could be implemented with Git?

Answer 1

1. Yes, the repository would be the equivalent of its first level

2. No! In Git you have access to the entire repository, you can’t just download a folder.

3. I see no reason for you to divide projects into repositories or sub-repositories, if they are part of the same Solution, the complexity would only increase. However, the use of module is interesting if you have a modular architecture, for example, an e-commerce and that in each module of the application stay in the performance of a team, sales, inventory, etc... You could download only application module pertaining to your work.

You can structure the folders in Git like this tip from the Microsoft page you quote. Normally I do:

• \
• src
• doc
• README.MD

and within src (source), I place the structure of Solution, normally AS IS as created by Visual Studio.