Have a basic product and additional modules (to populate a DB). The product needs to be access to the whole team and only team-lead modules. One ISU can affect change and modules and project, respectively, they must be in the same branch.
How they can differentiate?
Now we have 2 repository, but it is inconvenient (due to the requirements ISU and branches).
Invested do not succeed (maybe I'm inept). Doesn't want to committing it-that in a nested repository.
project (repository for team-lead)
-core (repository for all. His team-lead repository does not load, and needs)
Write the issue in the main part of the project.
You can annotate (but this is not necessary if the developers themselves with a mustache) what turnips are affected by this change.
GitHub links he is able to do.
Or, consider the use of Hitlab, not Github. It is more suited for rap related.
Kaylah_Mraz82 answered on July 8th 19 at 15:44
No way. Individual changes. Module applications should be separated by abstraction. But changing the abstraction does not affect the modules. And Vice versa.
If the modules are strongly connected then it is necessary to throw them into the core.