Connecting one Github repository to several Aptana projects

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.

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)

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

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.

Leave a Comment