Allow multiple Git repositories to be active at once
This suggestion is migrated to Developer Community. Please use below link to view the current status.
This description has been modified by the admin.
This request is to have VS allow more than one Git repository be active at once. By allowing multiple repositories to be active at once, one can work with a solution that spans multiple repositories and also view histories and files of a submodule and parent repo at the same time.
We’re excited to let you know that we’ve begun planning for this feature. Please keep an eye out for further updates!
This is a critical requirement when writing enterprise level micro-service type of architecture. Otherwise, it slows down development and complicated the process where we need to use the console instead of visual studio to commit/push/sync things. VS becomes useless for these type of applications.
Please add this feature as it is really annoying to view the history of submodules. Many companies use Git for their SCM. Really appreciate if VS has full Git integration.
Please ... We use to work (with the old TFS version control) with solutions that uses several classlibs that are also used in other solutions.
The difficulty of reusing repos/classlibs across different solutions is very very anoying
John Goatstream commented
Absolutely essential for anyone working with submodules
Please, this is very necessary...
Jacek Blaszczynski commented
pretty much very basic feature for anyone working with git and VS
This is a real pain! Please can you add this asap Microsoft, Having to resort to the command line to achieve this is ridiculous.
Robert Wloch commented
Here's a step by step guide to reproduce the effect of the missing feature and an explanation why this is really important:
Brent Vierling commented
Yes please add support so when I have a solution open, I can see the status/branch of all the repositories contained in the solution, see changed files in all repos, and commit to multiple repos.
This feature request should include more details such as:
Including, but not limited to:
1. Viewing history at the function/procedure level
2. Committing to the submodule(s) and automatically update the superprojects submodule pointers
3. Blame support
4. Branching support
Brian Vind Borgstrøm commented
I have also been experimenting with the EZ git provider. It works, but some features are missing. I really hope that MS will improve the situation very soon.
This is a much needed feature.
It seems like like the Eazy Git provider can do the job (https://marketplace.visualstudio.com/items?itemName=jzoss.GitSourceControlProvider2015) - but it has some drawbacks.
MS really needs to provide a build-in first class VS GIT provider
John Preston commented
Support full functionality when opening a solution from a parent repo with individual projects spread across multiple submodules.
I used to open the header of another git repo in my solution and I would love to be able to do history/annotate on that file.
N Case commented
This seems like a shortcoming in the VS 2015 GitHub integration. I'm in a similar situation, (needing multiple repos for one Solution). Any hope of getting this supported in a near term update?
Ivan Gilchrist commented
Working on my node js apps, I split reusable code into modules, each with it's own package.json and git repo. In order to work in Visual Studio, I have to open separate instances of visual studio, rather than keep them all as projects in a single solution because I can only be connected to a single git repo at a time. It would be much nicer to have a single solution with all of my modules as projects, and be able to interact with each git repo easily.
Greg Grater commented
Agreed. I love the Git integration, but I need to support multiple repositories in a single VS .sln. VS 2015 support bower packages (which also require a repository per developed component). I'd love to be able to build my own bower components in separate git repo, through VSTS using a single VS 2015 .sln.