Reputation: 11963
Currently I am thinking of making something like this
The idea is that I want to have one shared library living in its own repository while each of the Solution (A/B/C) live in a separate repository. Solution (A/B/C) are going to link reference the share library repository.
This way I can reuse shared library for any of the potential new project that I am going to make.
The problem is, I do not know how to make pull request to work across repositories. Lets say I need to change something in Solution A which I would need to change shared library too. From what I have read I should be able to commit to both repositories at the same time but I couldn't find any documentation on how to make PR work.
Is this possible?
Upvotes: 0
Views: 3752
Reputation: 23
While I would like to say that create PR in your own repository. It enables you to merge also. But if you do clone others repository than you can add and then commit to PR. You can create folders in your repository and merge them. You can also create folders in clone ones repositories and you can commit them.Just like above (A/B/C) I think this can be in the form of new files and folders that refer to your main or clone repository and you share with yourself or with others.
Upvotes: 0
Reputation: 1848
The solution here would be to put the shared library in a git submodule in each of the repositories. That way, you can commit changes to the shared library from either of your repositories, and can even depend on different versions or branchs of it in each repository.
Upvotes: 4