如何在VS Code Repositories选项卡中实现父文件夹与特定子文件夹的Git变更独立显示（无需修改目录结构）

Absolutely, you can get the parent and child repositories to display their changes independently in VS Code—no need to rearrange your folder structure. Here's how to set it up properly:

1. Lock Down the Parent Repo's Ignore Rule #

First, make sure the child folder is permanently excluded from the parent repo's tracking:

• Open the parent folder's .gitignore file and add this line (the trailing slash ensures it targets the folder, not a file with the same name):

  SU SCRIPTS EXTRAS/
  

• If you previously tracked any files from the child folder in the parent repo, run this command in the parent directory's terminal to clear those cached entries (this won't delete your files, just remove them from Git's tracking):

  git rm --cached -r "SU SCRIPTS EXTRAS"
  

• Commit the .gitignore change to the parent repo so the rule is applied for good.

2. Configure VS Code to Handle Nested Repos #

VS Code has built-in support for multiple repositories in a workspace, but you need to ensure both repos are recognized separately:

• Go to the Source Control tab (the Git icon on the left sidebar).
• Click the dropdown menu at the top of the tab (it will show your current repo name, like "SU (EDIT)").
• Select Add Repository and choose the child folder ("SU SCRIPTS EXTRAS") to add it to your workspace explicitly.
• Now, you can switch between the two repos using that same dropdown—each repo's modified files will only appear when you have it selected.
• If you still see cross-repo changes after adding both, reload the VS Code window (Ctrl+Shift+P or Cmd+Shift+P, then search for "Reload Window") to refresh the source control state.

3. Verify Git is Working Independently #

To confirm everything is set up correctly outside VS Code:

• Open a terminal in the parent folder and run git status—you should only see changes to files outside the child folder.
• Open a terminal in the child folder and run git status—it should show only its own changes, with no reference to the parent repo.

Troubleshooting #

If VS Code still mixes the changes:

• Check if any third-party source control extensions are interfering—try disabling them temporarily to see if the issue goes away.
• Ensure you haven't accidentally added the child folder as a submodule in the parent repo (run git submodule status in the parent folder; if you see an entry, you can remove it with git submodule deinit -f "SU SCRIPTS EXTRAS" followed by git rm -f "SU SCRIPTS EXTRAS").

内容的提问来源于stack exchange，提问作者rodrigotrovao