在AppHarbor上使用子模块

问题描述

我知道AppHarbor不支持当前的Git子模块（按照，我只是做了一个快速测试，证实了它）

但是，有没有另一种方法？

我目前有一个，我想将其用作我的子模块的远程主机，并且我需要创建一些其他的GitHub仓库来使用这个代码库（在App_Data内容中发生的唯一变化）。

使用Git子模块看起来像一个完美的解决方案，但是，当然，这个问题是它的内容不会被部署到AppHarbour。

所以除了在主GitGub Repository上创建一个硬拷贝（在文件系统上）之外，还有其他的选择吗？

解决方案

实际上，我发现了一种使用Git SubTree Merge来完成此操作的更好方法。这比子模块好得多，因为我确实希望能够：

• 有本地（合并）的文件


• 能够进行更改


• 具有原始存储库的完整历史记录。

以下是有关Git子树合并的更多详细信息：

>

I know that current Git submodules are not supported by AppHarbor (as per this support ticket and I just did a quick test that confirmed it)

BUT, is there another way?

I currently have a GitHub repository that I want to use as my submodule's remote master, and I need to create a number of other GitHub repositories that use this codebase (with the only changes happening inside the App_Data contents).

Using a Git submodule seems like a perfect solution, BUT, of course that problem is that its contents will not be deployed to AppHarbour.

So apart from creating a hard-copy (on the file system) of the master GitGub Repository, is there another alternative?

解决方案

I actually found a better way to do this using Git SubTree Merge. That works much better than submodules, since I do want to be able to:

• have the local (merged) files there
• be able to make changes to then
• have the full history of the original repositories.

Here are more details about Git's subtree merge:

• http://help.github.com/subtree-merge/
• http://progit.org/book/ch6-7.html

这篇关于在AppHarbor上使用子模块的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！