将一个Github存储库连接到几个Aptana项目 [英] Connecting one Github repository to several Aptana projects

问题描述

有没有办法将一个Github存储库连接到Aptana中的几个不同项目？换句话说，在不同的Aptana项目中有不同的目录连接到一个Github仓库？

Is there a way to connect one Github repository to several different projects in Aptana? In other words, to have different directories in a single Github repository connected to different Aptana projects?

我需要这个能力，因为我是一个在许多项目上工作的自由职业者，我不希望为Github支付$$$负担。

I need this ability since I'm a freelancer who works on many projects, and I don't wish to pay loads of $$$ to Github. This used to be possible with SVN.

推荐答案

一个GitHub仓库本身没有任何连接，它只包含一个集合。
如果在这些文件中有几个Aptana项目，那么您可以在本地克隆后使用这些项目。

A GitHub repo in itself isn't connected to anything, it only contains a set of files.
If, amongst those files, you have several Aptana projects, you can use those once you have clone locally.

但是，如果你只想克隆GitHub仓库的一个部分以获得其中的一个项目，这是不可能的（不支持filepath的部分克隆））

However, if you want to clone only a part of the GitHub repo in order to get only one of those projects, this isn't possible (partial clones by filepath aren't supported)

如果您只需要一个 GitHub仓库，不同的Aptana项目在不同的分支。

然后您可以克隆多次相同的回购，并根据您的项目签出不同的分支。

既然git1.7.10 + ，你甚至可以 git clone 理由

If you want only one GitHub repo, then store your different Aptana project in separate branches.
You can then clone multiple times the same repo, and checkout a different branch depending on your project.
Since git1.7.10+, you can even git clone just one branch out of your repo!

git clone --single-branch

仅克隆通向单个分支尖端的历史记录， code> - branch 选项或主分支远程的HEAD指向。

使用 - 深度选项，这是默认值，除非 - 无单分支被用于获取所有分支尖端附近的历史记录。

Clone only the history leading to the tip of a single branch, either specified by the --branch option or the primary branch remote's HEAD points at.
When creating a shallow clone with the --depth option, this is the default, unless --no-single-branch is given to fetch the histories near the tips of all branches.

但是这可能与浅层克隆有关，例如：

But that may have limitations associated with shallow clone, ie:

浅层存储库有许多限制（你不能从中克隆或取出，也不能从中推入或取出），但如果你只关心一个历史悠久的大型项目的近期历史，那么它就足够了，希望发送修补程序作为补丁。

A shallow repository has a number of limitations (you cannot clone or fetch from it, nor push from nor into it), but is adequate if you are only interested in the recent history of a large project with a long history, and would want to send in fixes as patches.

这篇关于将一个Github存储库连接到几个Aptana项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！