78a8760cfa
Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com> Co-authored-by: Sam Browning <106113886+sabrowning1@users.noreply.github.com> Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>
1.3 KiB
1.3 KiB
title, versions, topics, type, intro, allowTitleToDifferFromFilename
| title | versions | topics | type | intro | allowTitleToDifferFromFilename | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Problem with controller repository |
|
|
reference | If you see this warning, update your controller repository to a private repository. | true |
{% data reusables.code-scanning.mrva-beta %}
About this warning
Publicly visible controller repository can't be used to analyze private repositories. NUMBER private repositories were not analyzed.
If you run variant analysis on a custom list of repositories, you may receive this warning as a banner in {% data variables.product.prodname_vscode %}, where NUMBER is the number of private repositories that have not been analyzed.
Confirming the cause of the problem
When you run variant analysis, you'll see any errors and warnings displayed in the "Variant Analysis Results" view.
Fixing the problem
To 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 "AUTOTITLE."