Feature request: Support grouping "Cloned" repositories by user and organization (like in "Not Cloned")

[maddes8cht]

Hello! First of all, thank you for this extension – it’s an incredibly helpful tool for working across multiple repositories in VSCode, and I use it on a daily basis.

Description

I noticed the following behavior when working with repositories that belong to organizations I own or maintain:

Repositories from an organization I created appear under the Not Cloned tree in a dedicated branch (e.g., org-example) – which is great!

It looks like this:

Not Cloned
├── my-user
│   ├── repo-1
│   └── repo-2
├── my-organization
│   ├── sample-repo
│   └── another-tool

However, once I clone such a repository into my default GitHub directory (configured via githubRepositoryManager.defaultCloneLocation), it shows up under Cloned togehter with my regular Cloned list.

Also, cloned repositories from organizations are shown with the prefix "org-name/repo-name" in the tree view, while my personal repositories under Cloned show just "repo-name".

Steps to reproduce

• Create an organization on GitHub (e.g., org-example)
• Create a repository under that organization (e.g., sample-repo)
• Clone that repository into your configured GitHub folder via this extension

It appears under Cloned without further differentiation. So, it looks like this:

Not Cloned
├── repo-1
├── repo-2
├── my-organization/sample-repo
├── my-organization/another-tool

Suggestion

It would be incredibly helpful if cloned repositories could mirror the same hierarchical structure as shown under “Not Cloned”, such as:

Cloned
├── my-user
│   ├── repo-1
│   └── repo-2
├── my-organization
│   ├── sample-repo
│   └── another-tool

This would:

• Align visual grouping between Not Cloned and Cloned
• Improve clarity for users who use organizations to structure their personal or team-based work
• Reduce confusion between truly “external” projects and those that are owned but just not part of the user account

Optional

This behavior could be made configurable, so that users who prefer the current flat view can keep it.

Thanks again for the great extension – I’d love to see this improvement in a future update!

Best regards,

Maddes8cht

[ftzi]

Hi!

I agree and appreciate the idea.

Next month I will have time for it.

Stay tuned! 😄