Microsoft/vscode

Multiple Repos with git worktrees in worspace

Open

#257,396 opened on Jul 23, 2025

View on GitHub
 (14 comments) (0 reactions) (1 assignee)TypeScript (10,221 forks)batch import
bughelp wantedscm

Repository metrics

Stars
 (74,848 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

Hi,

I have searched now for a while but not found anything related to the issue I have. As I am working on multiple repositories with multiple branches I create my own workspace. In the workspace there are always the repositories mapped using worktree structures. An example:

Repo A .git -> story -> this_is_user_story_a -> this_is_user_story_b

Repo B -> story -> this_is_user_story_a -> this_is_user_story_b

Then I have two workspaces that are created like:

{
  "folders": [
    {
      "name": "Repo A",
      "path": "path/to/this_is_user_story_a"
    },
    {
      "name": "Repo B",
      "path": "path/to/this_is_user_story_a"
    }
}

The issue now is that in VS-Code View it does not show me the repository names but there I see twice:

this_is_user_story_a this_is_user_story_a

Is there any setting to tell the source view the correct name for the repo or a possibility to add such a feature?

Contributor guide

Research direction
Investigate how VS Code resolves repository names from workspace folders, especially with git worktrees. Look at the Source Control view implementation and consider adding a configuration option to set a custom name per workspace folder or automatically detect the parent repository name from the worktree's .git file.
Tech stack
typescript
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65