Version a "starter kit" to work upon in other projects

Question

All my projects have the same structure, base files (each containing some code).

Things I would like :

Version this code ;
Use it in other projects ;
Be able to update it in those projects ;
Only add code in those files, specific to each project (don't need to remove or to alter existing code).

I made some research. Using a package manager wouldn't suit my needs as i would like to add code to the package. I then found git submodules and subtrees and the latter seems to do the job.

What do you think about it ? Am I going in the right path by choosing subtrees or is there a better method ? Should I be using a complete different solution ?

Thanks guys

[EDIT]

More infos :

This "starter kit" is somewhat like a framework. I'm considering to build it in a way that doesn't need to edit its files in other projects but that would add constraints.

I don't think submodules would fit as i need to work on the code ;
Each project needs its own repo.

score 0 · Answer 1 · answered May 29 '16 at 15:08

0

Just make a master git repo, and clone that; you can have different branches for different variations of your base files.

This is pretty basic git usage.

answered May 29 '16 at 15:08

Marcus Müller

34,677
4
53
94

Creating one branch per project in the "starter kit" repo is not a good idea. Each project needs its own repo for multiple reasons. – Andréa Maugars May 29 '16 at 15:34
@AndréaMaugars not per project, per "skeleton variation". – Marcus Müller May 29 '16 at 15:40
And I didn't say you should put all projects in the same, repo @AndréaMaugars. I said you should clone a "template repo". That's different, fundamentally. – Marcus Müller May 29 '16 at 15:41

marisbest2 · Answer 2 · 2016-05-29T15:20:32.253

0

This seems overly complicated, but depending on how similar the codebase is and whether they are actually different projects you might want to use branches or make one repo with the shared code and then just clone (or to be fancier, add as a submodule) that into the repos for other projects. So if your shared code is shared and you have projects foo and bar you'd make 3 separate repos and clone (or submodule add) shared into foo and bar. It really depends on how often you'll be updating shared and how separate foo and bar are

edited May 29 '16 at 15:20

answered May 29 '16 at 15:13

marisbest2

1,346
2
17
30

`foo` and `bar` might be completely different projects but they will be built upon the same structure and code. My understanding of submodule is quite limited. I think the fact i want to edit the submodule in each project will be problematic. – Andréa Maugars May 29 '16 at 15:32

Version a "starter kit" to work upon in other projects

2 Answers2