{"meta":{"title":"Problem with controller repository","intro":"If you see this warning, update your controller repository to a private repository.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/reference","title":"Reference"},{"href":"/en/code-security/reference/code-scanning","title":"Code scanning"},{"href":"/en/code-security/reference/code-scanning/codeql","title":"CodeQL"},{"href":"/en/code-security/reference/code-scanning/codeql/codeql-for-vs-code","title":"CodeQL for VS Code"},{"href":"/en/code-security/reference/code-scanning/codeql/codeql-for-vs-code/controller-repository-warning","title":"Controller repository warning"}],"documentType":"article"},"body":"# Problem with controller repository\n\nIf you see this warning, update your controller repository to a private repository.\n\n## About this warning\n\n```text\nPublicly visible controller repository can't be used to analyze private repositories. NUMBER private repositories were not analyzed.\n```\n\nIf you run variant analysis on a custom list of repositories, you may receive this warning as a banner in Visual Studio Code, where NUMBER is the number of private repositories that have not been analyzed.\n\n## Confirming the cause of the problem\n\nWhen you run variant analysis, you'll see any errors and warnings displayed in the \"Variant Analysis Results\" view.\n\n## Fixing the problem\n\nTo analyze private repositories, you should edit your settings to update your controller repository to a private repository. For information on how to edit the controller repository, see [Customizing settings](/en/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/customizing-settings#configuring-settings-for-variant-analysis)."}