Version Control: Git submodule tree view

[Awbmilne]

I do a lot of work with repositories and submodules.
The biggest issue I come across is when using the same submodule in multiple repos of a multi-root workspace.

All the submodules show up in a plain list with just the name. This makes it hard to distinguish which repo each submodule belongs to:

Folder Structure:
├┬ Repo_A
│└─┬ Sub_A
│  └ Sub_B
├┬ Repo_B
│└─┬─ Sub_A
│  ├─ Sub_B
│  └┬ Sub_C
│   └─── Sub_Sub_A

Git Source Control Providers:
- Repo_A
- Sub_b
- Sub_b
- Sub_C
- Sub_A
- Repo_B
- Sub_Sub_A
- Sub_A

It would be amazingly convenient if there was a tree view like the Explorer.
This would make working with nested and numerous submodules a breeze.

(Yes, I know I could do it with the command line, and for commits/merges I do. But the changes view is really nice for keeping track of whats going on)

[ArturoDent]

There is a tree view for scm view. See https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_47.md#view--sort

[Awbmilne]

@ArturoDent
The mentioned release notes are indicating tree view for the changes section, not the actual repo list.

I have the changes setup with tree view, but the repos and submodules are still a plain list.

[Awbmilne]

Another thing I have recently noticed:

When checking out submodules to specific versions (tags), some submodules show the tag name and some show the commit hash:

Im sure everyone has their preference, but it seems like showing the tag name when a repo is checked out with "HEAD detached" would be the most informative format. Falling back on the commit hash when there is no tag present at that commit.

[joaomoreno]

The source control providers view is now gone, so this feature becomes harder to implement.

[NotWearingPants]

Duplicate of #43951