In the company I work with, we use Visual Studio 2013 and TFVC to version the projects.
I am accustomed to Source Control Explorer , can give Get Latest Version at any level (any repository, a project group, just a project or a specific file ), create Branch and see clearly 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, a group of projects or even just a specific project. Each project was organized in 3 Branch (Development, Main and Release), all just an exact copy. So the developers worked on Development
and then we could do the Merge on Main
to then send it to Release
. So when a bug appears in production, we resolve directly to Release
, publish and then replicate the patch to the other Branchs , and the game follows.
Now it has been decided to move to Git, and I was responsible for the migration, but I'm having a hard time putting together the folder structure (I can already understand the commands and many concepts used).
Looking at my old structure in TFVC , would it be possible to create something similar? (I know that Branchs will no longer be seen in the same way.)
Let's go to the checklist:
I've seen a bit about submodule , it might be an option in this context?
I was also passionate about this Microsoft tip , would you be able to implement it with Git?