-
Notifications
You must be signed in to change notification settings - Fork 34.8k
Description
- VSCode Version: Code 1.18.0 (dcee220, 2017-11-08T21:22:49.932Z)
- OS Version: Windows_NT x64 6.1.7601
- Extensions:
Extension | Author (truncated) | Version |
---|---|---|
cpptools | ms- | 0.14.0 |
Steps to Reproduce:
We use some command line tools from ARM to organise our project. This tools rely on special lib files to establish dependencies between modules. Each module should be an independent repository (git repositories in our case). So once all the references are deployed (the tools will "git clone" the indicated repositories in the lib files) the folder structure would look like this (folders in bold):
- project_folder (git repo)
- module1.lib
- module2.lib
- module1 (git repo)
- module3.lib
- module3 (git repo)
- module2 (git repo)
If we add project_folder as the root folder, the source control tab will only track the changes done in project_folder.
If we use the new multi-root project feature and also add module1, module2, and module3 to the workspace; we still find that only the changes in project_folder are tracked.
Nevertheless, if we add the folder in an strict reverse nesting order in the following manner:
- With an empty project open module3 as root folder
- Add folder to workspace... module2
- Add folder to workspace... module1
- Add folder to workspace... project_folder
Then we see that the source control view displays the several source control providers correctly.
Reproduces without extensions: Yes