-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
info-neededIssue requires more information from posterIssue requires more information from poster
Description
In some projects, monorepos with submodules are kept up to date with the latest commits. In others, they are centralized storage and are often behind the submodules.
In the later case, VSCode ends up highlighting every submodule as a change. For instance, take this case:
On branch master
Your branch is up to date with 'origin/master'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
(commit or discard the untracked or modified content in submodules)
modified: submodules/app1 (modified content)
modified: submodules/app2 (new commits)
modified: submodules/app3 (new commits)
modified: submodules/app4 (new commits)
modified: submodules/app5 (new commits)
modified: submodules/app6 (new commits)
no changes added to commit (use "git add" and/or "git commit -a")
Right now, app1 through app6 are highlighted as changed. I'd like to request an option called Git: Ignore new commits in submodules that would remove the highlighting from app2 through app6.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
info-neededIssue requires more information from posterIssue requires more information from poster