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
@@ -83,6 +85,65 @@ If you have set up code coverage, the `{% data variables.code-quality.pr_comment
83
85
84
86
Each {% data variables.product.prodname_codeql %} analysis will use {% data variables.product.prodname_actions %} minutes and can be seen on the **Actions** tab of the repository as a run of the dynamic "{% data variables.code-quality.workflow_name_actions %}" workflow.
85
87
88
+
## How enablement works across your enterprise
89
+
90
+
{% data variables.product.prodname_code_quality_short %} is controlled at three levels, so you can decide how much autonomy to give organizations and repositories:
91
+
92
+
***Enterprise:** An enterprise owner must first allow {% data variables.product.prodname_code_quality_short %} for the enterprise. Until they do, organization owners cannot enable it.
93
+
***Organization:** Organization owners control which repositories have {% data variables.product.prodname_code_quality_short %} enabled or disabled, by granting access to all repositories, a selected list, or repositories that match a filter. They can also enforce these settings so that repository administrators cannot change them.
94
+
***Repository:** Repository administrators can enable or disable {% data variables.product.prodname_code_quality_short %} for individual repositories, unless organization-level enforcement applies.
95
+
96
+
When {% data variables.product.prodname_code_quality_short %} is enabled on a repository, {% data variables.product.prodname_codeql %} analysis runs via {% data variables.product.prodname_actions %} and surfaces findings in pull requests and on the default branch. Developers see quality checks and annotations on their pull requests.
97
+
98
+
## Organization-level repository access
99
+
100
+
At the organization level, you control {% data variables.product.prodname_code_quality_short %} with a single **Repository access** setting. This setting determines which repositories have {% data variables.product.prodname_code_quality_short %} enabled and which have it disabled: repositories within your selection are enabled, and repositories outside your selection are disabled.
101
+
102
+
> [!IMPORTANT]
103
+
> Changing the **Repository access** setting can both enable **and** disable {% data variables.product.prodname_code_quality_short %} across many repositories at once. For example, if you enable {% data variables.product.prodname_code_quality_short %} for repositories matching a filter, any repository that does not match the filter is disabled. Before your change is applied, a dialog shows the total number of enabled and disabled repositories, along with the billing impact.
104
+
105
+
### Repository access options
106
+
107
+
You can apply one of the following options at a time.
108
+
109
+
| Option | Behavior |
110
+
| ------ | -------- |
111
+
|**No repositories**| Disables {% data variables.product.prodname_code_quality_short %} for all current and future repositories in the organization. |
112
+
|**Let repositories decide**| The organization neither enables nor disables {% data variables.product.prodname_code_quality_short %}. Repository administrators choose whether to enable it for their own repositories. This option cannot be enforced. |
113
+
|**All repositories**| Enables {% data variables.product.prodname_code_quality_short %} for all current and future repositories. |
114
+
|**Selected repositories**| Enables {% data variables.product.prodname_code_quality_short %} for a specific list of repositories that you choose. Repositories you do not select are disabled, and new repositories are not enabled automatically. Best for pilots or exceptions. |
115
+
|**Matching a filter**| Enables {% data variables.product.prodname_code_quality_short %} for repositories that match a filter you define, now and in the future. Repositories that do not match are disabled. See [Filtering repositories](#filtering-repositories). |
116
+
117
+
### Filtering repositories
118
+
119
+
When you choose **Matching a filter**, you create a dynamic filter that automatically enables {% data variables.product.prodname_code_quality_short %} for existing and future repositories that match your criteria. This is useful for ongoing governance at scale.
120
+
121
+
You can filter on any combination of the following criteria:
122
+
123
+
***Visibility:** Whether repositories are public, private, or internal. Useful for broad policies, such as enabling {% data variables.product.prodname_code_quality_short %} for all private repositories.
124
+
***Fork status:** Whether repositories are forks. Useful when forks should not consume analysis resources.
125
+
***Custom property:** Whether repositories have a specific custom property value. For example, you could target repositories with a `team:platform` property.
126
+
127
+
All conditions in a filter are combined with `AND`, so a repository must match every condition to be enabled. You can also exclude repositories that match specific conditions.
128
+
129
+
### Enforcing access
130
+
131
+
By default, repository administrators can change {% data variables.product.prodname_code_quality_short %} settings for their own repositories. To prevent this, enable **Enforce access**.
132
+
133
+
Enforcement locks in both the enabled and disabled states set by your **Repository access** option, so repository administrators cannot override them. This improves consistency across your organization, but reduces flexibility for individual repository administrators.
134
+
135
+
* Enforcement applies to most **Repository access** options you select, including **No repositories**, which enforces {% data variables.product.prodname_code_quality_short %} as disabled.
136
+
* Enforcement is not available with **Let repositories decide**, which intentionally leaves the choice to repository administrators.
137
+
138
+
## Planning your rollout
139
+
140
+
Because enabling {% data variables.product.prodname_code_quality_short %} can affect many repositories at once and each analysis consumes {% data variables.product.prodname_actions %} minutes, plan how you roll it out across your organization:
141
+
142
+
***Start with a pilot group.** Enable a small, representative set of repositories first—for example, by selecting them individually or matching a custom property—so you can validate results before expanding.
143
+
***Check your {% data variables.product.prodname_actions %} capacity.** Confirm your runners can absorb the additional load before you enable {% data variables.product.prodname_code_quality_short %} broadly.
144
+
***Decide whether to enforce enablement.** Enforcement gives you consistent coverage and prevents repository administrators from opting out, but it removes their flexibility. Leaving enforcement off during a pilot lets teams opt in and out as they learn.
145
+
***Expand once results are trusted.** After you've confirmed that analysis runs smoothly and developers understand the findings, widen your selection or filter to cover more repositories.
146
+
86
147
## Next steps
87
148
88
149
***For your repository or organization:** Turn on {% data variables.product.prodname_code_quality_short %} to start generating results. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/enable-code-quality).
Copy file name to clipboardExpand all lines: content/code-security/how-tos/maintain-quality-code/enable-code-quality.md
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,13 @@
1
1
---
2
2
title: Enabling {% data variables.product.prodname_code_quality %}
3
3
shortTitle: Enable Code Quality
4
-
intro: Use {% data variables.product.prodname_code_quality_short %} to automatically catch, fix, and report on code quality issues in pull requests and on your default branch.
4
+
intro: Enable {% data variables.product.prodname_code_quality_short %} across your organization's repositories to automatically identify and remediate code quality issues at scale, helping you maintain consistency and reduce operational risk.
5
5
versions:
6
6
feature: code-quality
7
7
product: '{% data reusables.gated-features.code-quality-availability %}'
8
8
permissions: '{% data reusables.permissions.code-quality-repo-enable %}'
> If your organization has configured caching of private registries, these will be available for code quality analysis to use to resolve dependencies. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries#code-quality-access-to-private-registries).
39
41
40
-
## Enabling {% data variables.product.prodname_code_quality_short %} for an organization
42
+
## Enabling {% data variables.product.prodname_code_quality_short %} for your organization
41
43
42
-
You can enable or disable {% data variables.product.prodname_code_quality_short %} for all repositories in an organization at once.
44
+
{% data reusables.code-quality.code-quality-org-targeting-preview-note %}
45
+
46
+
At the organization level, you control {% data variables.product.prodname_code_quality_short %} with a single **Repository access** setting. This gives you granular options, from enabling every repository to targeting a specific list or a dynamic filter, so you can pilot {% data variables.product.prodname_code_quality_short %} intentionally and roll it out at your own pace. Repositories within your selection are enabled, and repositories outside your selection are disabled.
47
+
48
+
For the available access options, and how filtering and enforcement work, see [AUTOTITLE](/code-security/code-quality/concepts/about-code-quality#organization-level-repository-access).
43
49
44
50
{% data reusables.organizations.navigate-to-org %}
45
51
{% data reusables.organizations.org_settings %}
46
52
1. In the sidebar, under "Security", click **{% data variables.code-quality.code_quality_ui_settings %}**.
47
-
1. Next to "Enable Code Quality", use the toggle to enable {% data variables.product.prodname_code_quality_short %} for all repositories.
53
+
1. Under "Repository access", select an option from the dropdown menu.
54
+
* If you selected **Selected repositories...**, choose the repositories you want to enable.
55
+
* If you selected **Matching a filter...**, define your filter.
56
+
1. Optionally, to prevent repository administrators from changing these settings, enable **Enforce access**.
57
+
1. If your change enables or disables {% data variables.product.prodname_code_quality_short %} on any repositories, a "Review enablement and billing changes" dialog appears, showing the total number of enabled and disabled repositories and the associated costs. Review the details, then click **Confirm**.
58
+
59
+
Your changes are saved automatically and begin to propagate immediately. In large organizations, it can take several minutes for the changes to apply across all repositories.
48
60
49
61
## Next steps
50
62
51
63
***For your repository:** Explore your code quality findings and merge your first fix. See [AUTOTITLE](/code-security/tutorials/improve-code-quality/quickstart).
52
64
***Add code coverage:** Upload test coverage reports to see coverage results directly on pull requests. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/set-up-code-coverage).
53
-
***For your organization:** Understand the code health of your repositories at a glance. See [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality).
65
+
***For your organization:** Understand the code health of your repositories at a glance. See [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/explore-code-quality).
Copy file name to clipboardExpand all lines: content/copilot/reference/ai-models/model-hosting.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ contentType: reference
16
16
17
17
## OpenAI models
18
18
19
-
{% data reusables.copilot.gpt-55-promo-period %}
20
-
21
19
Used for:
22
20
23
21
* {% data variables.copilot.copilot_gpt_5_mini %}
@@ -105,7 +103,7 @@ Used for:
105
103
106
104
* {% data variables.copilot.copilot_kimi_k27_code %}
107
105
108
-
{% data variables.copilot.copilot_kimi_k27_code %} was developed by Moonshot AI. It is an open-weight model that may be less aligned than other {% data variables.product.prodname_copilot_short %} models, with an elevated risk of producing harmful content. {% data variables.product.github %}'s content filtering applies, but you should review the [{% data variables.copilot.copilot_kimi_k27_code %} model card](https://huggingface.co/moonshotai/Kimi-K2.7-Code) and conduct your own evaluations before enabling it.
106
+
{% data variables.copilot.copilot_kimi_k27_code %} was developed by Moonshot AI. It is an open-weight model. {% data variables.product.github %}'s content filtering applies, but you should review the [{% data variables.copilot.copilot_kimi_k27_code %} model card](https://huggingface.co/moonshotai/Kimi-K2.7-Code) and conduct your own evaluations before enabling it.
109
107
110
108
When using {% data variables.copilot.copilot_kimi_k27_code %}, input prompts and output completions continue to run through {% data variables.product.prodname_copilot %}'s content filters for public code matching, when applied, along with those for harmful or offensive content.
| {% data variables.copilot.copilot_gemini_3_flash %} |`v1.115.0`and later |`17.14.22` or `18.1.0`and later|`1.5.62`and later |`0.46.0`and later |`0.14.0` and later|
136
-
| {% data variables.copilot.copilot_gemini_31_pro %} |`v1.115.0`and later |`17.14.22` or `18.1.0`and later|`1.5.62`and later |`0.46.0`and later |`0.14.0` and later|
137
-
| {% data variables.copilot.copilot_gemini_35_flash %} |`v1.115.0`and later |`17.14.22` or `18.1.0`and later|`1.5.62`and later |`0.46.0`and later |`0.14.0` and later|
138
-
| {% data variables.copilot.copilot_gpt_52_codex %} | No minimum listed |`17.14.19` or `18.0.0`and later|`1.5.61`and later |`0.45.0`and later |`0.13.0` and later|
139
-
| {% data variables.copilot.copilot_gpt_53_codex %} |`v1.104.1`and later |`17.14.19`and later|`1.5.61`and later |`0.45.0`and later |`0.13.0` and later|
140
-
| {% data variables.copilot.copilot_gpt_54 %} |`v1.104.1`and later |`17.14.19`and later|`1.5.66`and later |`0.47.0`and later |`0.15.0` and later|
141
-
| {% data variables.copilot.copilot_gpt_54_mini %} |`v1.104.1`and later |`17.14.19`and later|`1.5.66`and later |`0.47.0`and later |`0.15.0` and later|
142
-
| {% data variables.copilot.copilot_gpt_55 %} |`v1.117`and later |`17.14.19`and later|`1.5.66`and later |`0.47.0`and later |`0.15.0` and later|
135
+
| {% data variables.copilot.copilot_gemini_3_flash %} |`v1.115.0`|`17.14.22` or `18.1.0`|`1.5.62`|`0.46.0`|`0.14.0`|
136
+
| {% data variables.copilot.copilot_gemini_31_pro %} |`v1.115.0`|`17.14.22` or `18.1.0`|`1.5.62`|`0.46.0`|`0.14.0`|
137
+
| {% data variables.copilot.copilot_gemini_35_flash %} |`v1.115.0`|`17.14.22` or `18.1.0`|`1.5.62`|`0.46.0`|`0.14.0`|
138
+
| {% data variables.copilot.copilot_gpt_52_codex %} | No minimum listed |`17.14.19` or `18.0.0`|`1.5.61`|`0.45.0`|`0.13.0`|
139
+
| {% data variables.copilot.copilot_gpt_53_codex %} |`v1.104.1`|`17.14.19`|`1.5.61`|`0.45.0`|`0.13.0`|
140
+
| {% data variables.copilot.copilot_gpt_54 %} |`v1.104.1`|`17.14.19`|`1.5.66`|`0.47.0`|`0.15.0`|
141
+
| {% data variables.copilot.copilot_gpt_54_mini %} |`v1.104.1`|`17.14.19`|`1.5.66`|`0.47.0`|`0.15.0`|
142
+
| {% data variables.copilot.copilot_gpt_55 %} |`v1.117`|`17.14.19`|`1.5.66`|`0.47.0`|`0.15.0`|
Copy file name to clipboardExpand all lines: content/rest/search/search.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Unless another sort option is provided as a query parameter, results are sorted
31
31
{% data reusables.enterprise.rate_limit %}
32
32
33
33
The REST API has a custom rate limit for searching. For authenticated requests, you can make up to
34
-
30 requests per minute{% ifversion fpt or ghec %} for all search endpoints except for the [Search code](/rest/search/search#search-code) endpoint. The [Search code](/rest/search/search#search-code) endpoint requires you to authenticate and limits you to 9 requests per minute{% endif %}. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute.
34
+
30 requests per minute{% ifversion fpt or ghec %} for all search endpoints except for the [Search code](/rest/search/search#search-code) endpoint. The [Search code](/rest/search/search#search-code) endpoint requires you to authenticate and limits you to 10 requests per minute{% endif %}. For unauthenticated requests, the rate limit allows you to make up to 10 requests per minute.
35
35
36
36
For information about how to determine your current rate limit status, see [Rate Limit](/rest/rate-limit/rate-limit).
> Organization-level repository targeting for {% data variables.product.prodname_code_quality %} is in {% data variables.release-phases.public_preview %} and subject to change.
0 commit comments