Opening all of them consumes a massive amount of resources, as does constantly watching them for changes.
Both of these ‘metarepo’ type setups contain ludicrous numbers of repositories, the overwhelming majority of which I am never going to touch. The inability to prevent the git extension from automatically recursing through every repository in a workspace is utterly infuriating whenever you’re dealing with a repo project or west workspace. There’s not much in the way of documentation around any of the git config settings… If these settings don’t prevent autodetection of repositories within the workspace, they have pretty misleading names… It would be good to have this laid out explicitly in the documentation somewhere as far as I’ve been able to find, it’s not. Could you please share your scenario in which you would like to disable repository detection completely? Thank you! We could probably improve on the documentation but we are also opened to behaviour change.
As of right now, the setting controls scanning repositories that are not in the root workspace folder which is being opened in VS Code.
(1 theme extensions excluded) A/B Experiments thanks for filing the issue. Setting git.autoRepositoryDetection to true, false, subFolders or openEditors seems to have no effect.Īfter setting git.autoRepositoryDetection to false (for both user and workspace) and then opening a workspace, Visual Studio Code still detects Git repositories from current, parent or subfolders.
0 kommentar(er)
