git - Splitting a repository with the possibility to later pull changes -


i have repository in have boilerplate code new projects.
have 2 projects 2 different clients. projects have resemblances. ideally if add new feature project x think useful other project want add non-specific code boilerplate , pull repo's of individual projects. possible?
don't want work branches in same repository since both projects installed on servers of clients capistrano (so can pull changes when doing deploy). , don't want client x able see code of other client.

you use built-in subtrees (or criticized alternative, built-in, called submodules).

and take @ git-subrepo project.

all options allow have nested repositories. in case, boilerplate repository nested inside clients' repositories. allow them pull boilerplate repository without needing share core code each other.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -