Allow multiple Git repositories in a single Team Project
The recommend approach to using TFS (TFSVC) is to have a single Team Project which contains multiple projects organised by using areas for tasks / bugs and folders in source control. However the recommended approach to using Git is to use multiple small repositories with a project per repository and then using submodules to glue things together. It is not feasible to have multiple projects in a single git repository because the repository becomes too large and even though there is sparse checkout now it doesn't help with some cases such as needing multiple remotes for a module (needing local changes to a 3rd party library as an example.)
When using git with TFS I'd like to have the ability to have multiple git repositories in a single Team Project so that the recommended approach to using TFS and Git can be followed. Something like using gitslave would be good too.
Deployed on 5/13 to the service. http://tfs.visualstudio.com/en-us/home/news/2013/may-13/
Roberto Luis Bisbe commented
What about this feature for on-premises versions of Visual Studio?
Please upvote this suggestion, because otherwise this sugestion is not very usefull:
Ulyses Rana Gotera commented
A colleague suggested to me that there should be a librarian for link libraries. They have done this in their previous company and he said that it is easy to maintain. At that time, GIT and team foundation server where not around. They were using Microsoft's Visual Source Safe.
I think it is still sound to have a group repositories (or projects) that the assign software librarian has control. In this manner, there is no need to create a feature in TFS tracking repositories in GIT.
Just my two cents.
Kuan Bartel commented
Note: I do not think that having multiple TFSVC repositories is really needed, just git. The main problem is that even though we can create multiple git repositories in TFS they each in-turn have their own Team Project and hence there is no link between the Team Projects. It is desirable to have a single Team Project to allow for easy planning and tracking of tasks and bugs across all teams and projects.