Github linked to other repositories

Question

I have a project that uses two repositories in github to work. When I submit my project to github, how do I link to these two repositories? Do I have to duplicate files in my own repo or a link to another repo for a specific revision, since I do not want it to be updated and cause incompatibility. I already created a github repository, what should I do?

Answer 1

You can use git submodules to “link” to other projects. See here http://help.github.com/submodules/

Answer 2

There is an alternative to submodules, which, it seemed to me, are more practical: a subtree .

According to this link, the advantages are as follows:

• Simple management of simple document management.
• The old version of git is supported (even before version 1.5.2).
• The subproject code is available immediately after the completion of the superproject clone.
• It doesn’t require users of your repository to learn anything new, they can ignore the fact that you are using a subtree to manage dependencies.
• the subtree does not add new metadata files, such as subodules doe (i.e...gitmodule).
• The contents of the module can be changed without having a separate copy of the repository elsewhere.

Answer 3

GitHub will also allow you to link to another repository in a comment on GitHub or in a commit. For example:

We should probably handle this with github/enterprise#59 

This will add an update to github/enterprise#59 problem with a link to your comment / commit.

Links to the repository repository

Of course, GitHub is all about social coding, but you can also have social repositories. You can refer to problems between repositories by specifying # in the user / repository . As soon as we see something like this, say github / enterprise # 59, we will definitely update issue 59 in the github enterprise repository and let you know what it referred to. This is part of the GitHub Flavored Markdown , which also has some of its own tricks.

Read more: https://github.com/blog/967-github-secrets