The Planning problem of Project Construction Branch

I haven"t done much multi-project development of a base code version before, but now I want to pull branches of each project. My plan is to first pull a set of common code as the backbone, which only contains the basic code and business logic that can be reused, and other versions as branches, each add projects on it and inherit these common codes. each project"s own business logic is written in its own project. If there is code reuse or the addition of common code is maintained in the trunk, other branch Synchronize backbone, specific each project"s own business logic is maintained in its own branch, I wonder if there is any problem with this? Do you have any good suggestions on how to do this in general?

May.01,2021

what language do you develop in? in the case of Java, common functions are generally extracted to a separate basic jar, instead of using source dependencies.
other languages, will use links to connect the point common library project (SVN,GIT specific operation is not the same), will not use branch management code to rely on

Menu