Limiting developer access to git repository for a website and how to deploy it

Question

I am considering taking on a new developer for my rails based website but, because I do not know them, I do not want them to have complete read access to my code. I only want them to be able to read and write to one directory.

Requirements:

I would also like them do be able to deploy their updates/changes.

Both myself and the developer use windows so symbolic linking is not a good idea...

I currently use capistrano to deploy the website but will use vlad or anything else that will work...

Background Reading

So, I have been reading about submodules, subtrees (apenwarr's git-subtree and the subtree merge strategy), giternal, piston, braid, etc, etc and I am completely flummoxed! Any help that can be provided would be greatly appreciated!

My current thoughts

I don't think that submodules are the right choice here because:

1) I would like to make as few changes as possible to the main repository

2) i) The developer would need access to the main repository to notify it of submodule changes... which defeats the purpose of making them work with a submodule.

ii) I could create a master repository that would reference the divided sections of the website but I have no idea how to do this or if it would even work.

Subtrees

If I understand them correctly, someone can work on the subtree and commit to it as if they had full access to only that part of the master repository. At first glance this seems to make them just exaclty what I need - especially since the master repository can reference the current HEAD of a subtree by default and doesn't need manual updating. Unfortunately I can't see how I would deploy the website with subtree nor can I tell if this is really want I want. There is a lot of conflicting opinion about submodules, subtrees etc and it is difficult to sort through it.

Thank you very much for your time reading this and any help that you can offer!

Answer 1

子模块：2）通过电子邮件或基于Web的系统向您发送“请求”。