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
Copy file name to clipboardExpand all lines: content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,6 @@ For repositories that are not eligible for default setup, you can configure adva
45
45
A repository must meet all the following criteria to be eligible for default setup, otherwise you need to use advanced setup.
46
46
47
47
* Advanced setup for {% data variables.product.prodname_code_scanning %} is not already enabled.
48
-
* Uses Go, JavaScript/TypeScript, Python, or Ruby.
49
48
{% data reusables.code-scanning.require-actions-ghcs %}
50
49
51
50
{% data reusables.code-scanning.default-setup-pre-enablement-explanation %}
Copy file name to clipboardExpand all lines: content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning.md
+3-8Lines changed: 3 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,11 +56,9 @@ Default setup uses the `none` build mode for {% data variables.code-scanning.no_
56
56
57
57
We recommend that you start using {% data variables.product.prodname_code_scanning %} with default setup. After you've initially configured default setup, you can evaluate {% data variables.product.prodname_code_scanning %} to see how it's working for you. If you find that something isn't working as you expect, you can customize default setup to better meet your needs. For more information, see [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/evaluating-default-setup-for-code-scanning).
58
58
59
-
### About adding non-compiled and compiled languages to your default setup
59
+
### About adding new languages to your default setup
60
60
61
-
If the code in a repository changes to include Go, JavaScript/TypeScript, Python, or Ruby, {% data variables.product.prodname_dotcom %} will automatically update the {% data variables.product.prodname_code_scanning %} configuration to include the new language. If {% data variables.product.prodname_code_scanning %} fails with the new configuration, {% data variables.product.prodname_dotcom %} will resume the previous configuration automatically so the repository does not lose {% data variables.product.prodname_code_scanning %} coverage.
62
-
63
-
Compiled languages are not automatically included in default setup configuration because they often require more advanced configuration, but you can manually select any {% data variables.product.prodname_codeql %}-supported compiled language for analysis.
61
+
If the code in a repository changes to include any {% data variables.product.prodname_codeql %}-supported languages, {% data variables.product.prodname_dotcom %} will automatically update the {% data variables.product.prodname_code_scanning %} configuration to include the new language. If {% data variables.product.prodname_code_scanning %} fails with the new configuration, {% data variables.product.prodname_dotcom %} will resume the previous configuration automatically so the repository does not lose {% data variables.product.prodname_code_scanning %} coverage.
64
62
65
63
## Configuring default setup for a repository
66
64
@@ -79,7 +77,6 @@ Compiled languages are not automatically included in default setup configuration
79
77
{% ifversion ghas-products %}
80
78
81
79

82
-
83
80
84
81
{% else %}
85
82
@@ -89,11 +86,9 @@ Compiled languages are not automatically included in default setup configuration
89
86
90
87
You will then see a "{% data variables.product.prodname_codeql %} default configuration" dialog summarizing the {% data variables.product.prodname_code_scanning %} configuration automatically created by default setup.
91
88
92
-
> [!NOTE]
93
-
> If your repository contains _only_ compiled {% data variables.product.prodname_codeql %}-supported languages (for example, Java), you will be taken to the settings page to select the languages you want to add to your default setup configuration.
94
89
95
90
1. Optionally, to customize your {% data variables.product.prodname_code_scanning %} setup, click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**.
96
-
* To add or remove a language from the analysis performed by default setup, select or deselect that language in the "Languages" section. If you would like to analyze a {% data variables.product.prodname_codeql %}-supported compiled language with default setup, select that language here.
91
+
* To add or remove a language from the analysis performed by default setup, select or deselect that language in the "Languages" section.
97
92
* To specify the {% data variables.product.prodname_codeql %} query suite you would like to use, select your preferred query suite in the "Query suites" section.
98
93
99
94
1. Review the settings for default setup on your repository, then click **Enable {% data variables.product.prodname_codeql %}**. This will trigger a workflow that tests the new, automatically generated configuration.
0 commit comments