You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using automatic project search (via projectManager.git.baseFolders), in case of complex git repositories, like the ones with nested repos or/and submodules, I find it rather confusing to have both the outer ("main") repo and inner sub-repos listed as separate projects.
My suggestion is to stop looking for nested git projects once a valid top-level one has been found, or introduce a setting to let the user control this behaviour.
Perhaps this is also relevant to other VCSs.
The text was updated successfully, but these errors were encountered:
When using automatic project search (via
projectManager.git.baseFolders
), in case of complex git repositories, like the ones with nested repos or/and submodules, I find it rather confusing to have both the outer ("main") repo and inner sub-repos listed as separate projects.My suggestion is to stop looking for nested git projects once a valid top-level one has been found, or introduce a setting to let the user control this behaviour.
Perhaps this is also relevant to other VCSs.
The text was updated successfully, but these errors were encountered: