Best practices for code/repository management

@giuseppemastrodonato Your "mother" repository should be added as an upstream remote, so you can pull changes into each "child" repository:

git pull upstream master

@martinbean can I add it as upstream also if the "Child" repository is a "modified" clone (so basically a completely different repo)? Or do I have to fork the mother and then add it as upstream of the child?

@giuseppemastrodonato You should be forking the parent repository, otherwise the child repository wouldn't have any common ancestor commits, and will probably give you a nasty merge conflict if you tried to pull the master branch of the parent repository into your child repository.

But, it's difficulties like this why a lot of content management systems have gone down the package route, in that the CMS is a package you install using Composer into a new or existing Laravel application, and then updating is a case of running composer update your/cms rather than trying to keep multiple Git repositories in sync with an upstream one.

Thank @martinbean, I will try with the fork way. Do you have any recommendation for the package development?

@giuseppemastrodonato Well a package can have its own routes, controllers, views, configuration etc. So a lot of CMS vendors these days are making their CMS a package that application developers can add to their composer.json file. That way, when a new CMS version is released, all you need to do is run composer update, rather than having to mess about pulling from other remotes in Git.