At the moment of writing I have let's say 4 micro services interoperating in order to build a bigger system.Every microservice has its own repo.What I'm thinking is that it would be useful to have  parent repositories that group the children microservices, adding them as git submodules.So if a developer needs to work and setup his dev env for: systemA made of ms1, ms2,m3 systemB made of ms2, ms3, ms5will just have to clone the system repository (already linking to ms dependencies)Or if I need to build a new system , i'll crete a new parent repository linking to git submodules ms dependenciesBasically the parent repo will contain nothing but link to submodules (don't know if they will need some more at this moment.. )For sure I'll face the problem of having a ms development shared across different System. So maybe that would be solved using different master branche on children repo (one for every parent production system)What do you think about this practice? Is it a good idea?Working with submodules could become tricky?
Is it a good idea to manage a group of repo microservices as submodules of a master repo?
git;microservices;dependencies