New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCM: Differentiate between submodules and normal repos #43951
Comments
Plus one for me. When I work in the parent directory of all my git projects, it causes all of my submodules to display as many times as they are included within other projects. An option to not display submodules in the source control providers list would be helpful. |
@joaomoreno This is not a duplicate of #40548 You are the one who changed the title in August from Please reopen and revert the title change, this is still an issue |
@joaomoreno I totally agree with @NotWearingPants. My issue is specifically related to submodules. #40548 would lessen the issue, but would not solve it. |
You're absolutely right, sorry about that. |
This extension can help solve this problem. https://marketplace.visualstudio.com/items?itemName=R.git-submodule-sort |
In this same vein, I've started to use multiroot workspaces pretty extensively (they're awesome....I no longer need to have several vscode windows open). The projects I'm working on span a number of git repos and so I have a few top level folders that I've added to my workspace and underneath those I have all my repos placed. The Explorer view has a nice tree structure so this works out nice and makes it very easy to jump between repos. However, the source control tab doesn't show that structure--it flattens all the repos out (even repos that are submodules). Is there anyway to get the source control pane to follow the folder structure the repos are organized into? |
+1 on this. When working on a ROS workspace it's common to have multiple repos potentially with repeating submodules and the current view doesn't allow easy differentiating between them - see attached screenshot. The only way I've found is to hover the mouse over a repo's name, which displays it's full path. |
i also needs the fix for that .. if i have two subModules in this directories:
.. i can sort them by path (in my user settings.json): |
Issue Type
Feature Request
I would like submodules to be nested underneath their parent repo in the Source Control Pane.
Description
I love the new submodule feature, but there are a couple of issues with the Source Control pane:
For most situations, this probably isn't an issue. But for some of my projects, it is a serious issue. For example, I have projects:
For development, I use a multi-root workspace with a directory structure something like this:
../A
)../A
and../B
)For continuous integration and deployment, I use submodules:
./.libs/A
and./.libs/B
)/builds/C/.libs/A
)While I could leave the submodules uninitialized on my dev machine, my workflow includes doing a build with submodules before I push, to ensure I haven't forgotten to update a submodule, because why waste CPU cycles on a CI build that's guaranteed to fail.
In this particular example, where B has A as a submodule, and C has A and B, I will have six repos (A, B, C, B/.libs/A, C/.libs/A, and C/.libs/B) show up in VSCode. While I can and do disable submodule discovery for these projects, that doesn't stop VSCode from picking them up when I open a file in a submodule.
VS Code Info
VS Code version: Code 1.20.1 (f88bbf9, 2018-02-13T15:34:36.336Z)
OS version: Windows_NT x64 10.0.16299
The text was updated successfully, but these errors were encountered: