I have a service that I am developing, which will consist of several "bits". It will be open source, so I want people to be able to see the project as a whole, check it out, make changes, etc., and not give people a list of different projects to check.
So, imagine that I have a project called "Flintstones" and it is made from "Barney", "Wilma" and "Bambam".
As far as I understand, if I did this with subtrees, then if a person checks "Flintstones", they see everything, but if they make changes to the code in Barney, they should merge this code back into the Barney repository. So this is bad, because people change the code and either do not know that it is a subtree or simply do not.
All examples of auxiliary modules say that they are used to embed common code in a project, but do I say correctly that if a person checks the “Flintstones” and makes changes to the “Barney” folder, then he simply does a regular commit and push, then Does this change go to Barney? The only drawback in this scenario is that they have to validate the project with additional syntax for validation subcategories?
I want to break it down so that the assemblies are only initiated and executed for that part of the project that has changed, so changes in Barney only cause Barney to build and test on my CI server (bamboo in this case). Over time, different people will work on different modules of the code, not even knowing about others.
source
share