Code exchange between separate projects / repositories?

I am working on a project locally using the git repository cloned from svn using git-svn. Now I need to add code from another svn repo. The code is modular, so the new code will be in a new subdirectory that does not overlap the existing code. I use git-svn in my local development environment, the intermediate server is svn checkout, and the live server is svn export.

In some context, I am working on two separate Drupal sites, each with its own svn repo. Site A has some custom modules that you must now add to site B. What is the best way to manage individual sites and repositories?

It seems like I might be better off setting up a third separate svn repository that contains modules that are distributed between sites. If so, what is the best way to work with two separate repositories in the same project?

EDIT : I am particularly interested in how others handle version control when mixing Drupal modules with custom modules on multiple sites. How can I improve the setting described in the last sentence of the first paragraph?

+3
source share
2 answers

You can use External Definitions to have subdirectories in your working copy of other repositories.

+5
source

Drupal 6? , // /example 1.com/modules, sites/example2.com/modules .., git .

http://drupal.org/node/231298, , D7, .

+1

Source: https://habr.com/ru/post/1783508/


All Articles