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: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,15 @@
1
1
# Docs changelog
2
2
3
+
**20 January 2026**
4
+
5
+
We published the first iteration of the [GitHub Copilot feature matrix](https://docs.github.com/en/copilot/reference/copilot-feature-matrix) to provide customers with the latest information about which Copilot features are available by which IDE/version.
6
+
7
+
Historically, keeping Copilot feature and IDE availability up to date has required manual coordination with the Docs team, which does not scale well with the increasing number of features. The goal of this document and its process is to enable product owners to directly maintain the Copilot feature and IDE availability information as part of their normal release workflow. The feature matrix provides a single, easy to update source of truth.
8
+
9
+
The feature matrix is in public preview so that customers have time to gather and submit feedback to us.
10
+
11
+
<hr>
12
+
3
13
**16 January 2026**
4
14
5
15
The following new articles support the public preview release of Copilot Memory:
permissions: '{% data reusables.permissions.enhanced-billing-platform %}'
29
30
shortTitle: Set up budgets
30
-
contentType: tutorials
31
+
contentType: how-tos
31
32
---
32
33
33
34
Budgets help you track and control spending on different products. To learn more, see [AUTOTITLE](/billing/concepts/budgets-and-alerts).
34
35
35
-
## Deciding on the type and scope for a budget
36
+
## Plan your budget type and scope
36
37
37
-
When deciding on the type and scope for a budget, remember that the use of metered products is applied towards **all applicable** budgets. If any applicable budget with "Stop usage when budget limit is reached" enabled is exhausted, additional usage is blocked.
38
+
Before you create a budget, it’s important to understand how budget types and scopes interact. Usage of metered products can count toward multiple applicable budgets at the same time, and if any budget with **Stop usage when budget limit is reached** enabled is exhausted, additional usage is blocked.
38
39
39
40

Copy file name to clipboardExpand all lines: content/code-security/concepts/code-scanning/about-code-scanning.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
@@ -36,7 +36,7 @@ If {% data variables.product.prodname_code_scanning %} finds a potential vulnera
36
36
{% endif %}
37
37
38
38
To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see
39
-
[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert). For information about API endpoints, see [AUTOTITLE](/rest/code-scanning).
39
+
[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert). For information about API endpoints, see [AUTOTITLE](/rest/code-scanning/code-scanning).
Copy file name to clipboardExpand all lines: content/code-security/concepts/security-at-scale/about-security-overview.md
+9-39Lines changed: 9 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ There are dedicated views for each type of security alert. You can limit your an
73
73
74
74
The application security team at your company can use the different views for both broad and specific analyses of your organization's security status. For example, the team can use the "Overview" dashboard view to track your organization's security landscape and progression. {% ifversion pre-security-configurations %}You can also use security overview to find a set of repositories and enable or disable security features for them all at the same time. For more information, see [AUTOTITLE](/code-security/security-overview/enabling-security-features-for-multiple-repositories).{% endif %}
75
75
76
-
You can find security overview on the **Security** tab for any organization. Each view shows a summary of the data that you have access to. As you add filters, all data and metrics across the view change to reflect the repositories or alerts that you've selected. For information about permissions, see [Permission to view data in security overview](#permission-to-view-data-in-security-overview).
76
+
You can find security overview on the **Security** tab for any organization. Each view shows a summary of the data that you have access to. As you add filters, all data and metrics across the view change to reflect the repositories or alerts that you've selected.
77
77
78
78
Security overview has multiple views that provide different ways to explore enablement and alert data.
79
79
@@ -97,49 +97,19 @@ You can find security overview on the **Security** tab for your enterprise. Each
97
97
98
98
As with security overview for organizations, security overview for enterprises has multiple views that provide different ways to explore data.
99
99
100
-
For information about permissions, see [Permission to view data in security overview](#permission-to-view-data-in-security-overview).
100
+
## Access to data in security overview
101
101
102
-
## Permission to view data in security overview
102
+
What you can see in security overview depends on your role and permissions in the organization or enterprise.
103
103
104
-
### Organization-level overview
104
+
In general:
105
105
106
-
If you are an **owner or security manager** for an organization, you can see data for all the repositories in the organization in all views.
106
+
***Organization owners and security managers** can view security data across all repositories in their organization.
107
+
***Organization members** can view data only for repositories where they have access to security alerts.
108
+
***Enterprise owners** can view aggregated security data in the enterprise-level security overview for organizations where they are an organization owner or security manager. To see repository-level details, they must have the appropriate role within the organization.
107
109
108
-
If you are an **organization or team member**, you can view security overview for the organization and see data for repositories where you have an appropriate level of access.
110
+
Security overview displays data only for repositories you have permission to view, and some views or actions may be limited based on your role.
109
111
110
-
{% ifversion secret-risk-assessment %}
111
-
112
-
> [!TIP] The Assessments view, which is not shown in the table below, is only available to organization owners and security managers.
113
-
114
-
{% endif %}
115
-
116
-
{% rowheaders %}
117
-
118
-
| Organization or team member with | Overview dashboard view | Risk and alerts views | Coverage view |
|`admin` access for one or more repositories | View data for those repositories | View data for those repositories | View data for those repositories{% ifversion pre-security-configurations %}, and enable and disable security features{% endif %} |
121
-
|`write` access for one or more repositories | View {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} data for those repositories | View {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} data for those repositories | No access |
122
-
|`read` or `triage` access for one or more repositories | No access | No access | No access |
123
-
| Security alert access for one or more repositories | View all security alert data for those repositories | View all security alert data for those repositories | No access |
124
-
| Custom organization role with permission to view one or more types of security alert | View allowed alert data for all repositories | View allowed alert data for all repositories in all views | No access |
125
-
126
-
{% endrowheaders %}
127
-
128
-
> [!NOTE]
129
-
> To ensure a consistent and responsive experience, for organization members, the organization-level security overview pages will only display results from the most recently updated 3,000 repositories. If your results have been restricted, a notification will appear at the top of the page. Organization owners and security managers will see results from all repositories.
130
-
131
-
For more information about access to security alerts and related views, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles#security).
132
-
133
-
### Enterprise-level overview
134
-
135
-
> [!NOTE]
136
-
> If you are an **enterprise owner**, you will need to join an organization as an organization owner to view data for the organization's repositories in both the organization-level and enterprise-level overview.{% ifversion secret-scanning-user-owned-repos %} {% data reusables.secret-scanning.secret-scanning-user-owned-repo-access %}{% endif %} For more information, see [AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise).
137
-
138
-
In the enterprise-level security overview, you can see data for all organizations where you are an **organization owner or security manager**.
139
-
140
-
{% ifversion ghec %}
141
-
If you're an owner of an {% data variables.enterprise.prodname_emu_enterprise %}, you can view data from user-owned repositories in security overview and filter by repository owner type. For more information on {% data variables.enterprise.prodname_managed_users %}, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users).
142
-
{% endif %}
112
+
For detailed, role-by-role permission information, including which views are available and how repository access affects visibility, see [AUTOTITLE](/code-security/reference/permissions/security-overview-permissions).
Copy file name to clipboardExpand all lines: content/code-security/concepts/security-at-scale/auditing-security-alerts.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,21 +70,21 @@ You can use the API to list and interact with security alerts, for example, gett
70
70
71
71
You can list all {% data variables.product.prodname_dependabot %} alerts for a repository, organization, or enterprise, or use path parameters to list only alerts that meet a specific set of criteria. For example, you might only want to list {% data variables.product.prodname_dependabot %} alerts for Maven that were dismissed. Alternatively, you can get full details for an alert or update the alert.
72
72
73
-
For more information, see [{% data variables.product.prodname_dependabot %} alerts](/rest/dependabot/alerts#about-dependabot-alerts).
73
+
For more information, see [AUTOTITLE](/rest/dependabot/alerts#about-dependabot-alerts).
74
74
75
75
### {% data variables.product.prodname_secret_scanning_caps %} alerts API
76
76
77
77
You can list all {% data variables.product.prodname_secret_scanning %} alerts for a repository, organization, or enterprise, or use path parameters to list only alerts that meet a specific set of criteria. Alternatively, you can get full details for an alert or update the alert.
78
78
79
79
To see which {% data variables.product.prodname_secret_scanning %} alerts were the result of a push protection bypass, filter the results for `"push_protection_bypassed": true`.
80
80
81
-
For more information, see [{% data variables.product.prodname_secret_scanning_caps %}](/rest/secret-scanning).
81
+
For more information, see [AUTOTITLE](/rest/secret-scanning).
82
82
83
83
### {% data variables.product.prodname_code_scanning_caps %} alerts API
84
84
85
85
You can list all {% data variables.product.prodname_code_scanning %} alerts for a repository, organization, or enterprise, or use path parameters to list only alerts that meet a specific set of criteria. Alternatively, you can get full details for an alert or update the alert.
86
86
87
-
For more information, see [{% data variables.product.prodname_code_scanning_caps %}](/rest/code-scanning).
87
+
For more information, see [AUTOTITLE](/rest/code-scanning/code-scanning).
Copy file name to clipboardExpand all lines: content/code-security/concepts/security-at-scale/choosing-a-security-configuration-for-your-repositories.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,8 @@ To start securing repositories in your organization with the {% data variables.p
43
43
If you are familiar with {% data variables.product.company_short %}'s security products, and you have specific security needs that the {% data variables.product.prodname_github_security_configuration %} can't meet, you can create and apply {% data variables.product.prodname_custom_security_configurations %}. With {% data variables.product.prodname_custom_security_configurations %}, you can:
44
44
45
45
* Edit the enablement settings for different security features
46
-
* Create several configurations for repositories with different security needs
47
-
* Control your usage and costs by including or excluding {% data variables.product.prodname_GH_code_security %} or {% data variables.product.prodname_GH_secret_protection %} features for a particular configuration
46
+
* Create several configurations for repositories to reflect their different levels of visibility, risk tolerance, and impact
47
+
48
+
You can also choose whether or not you want to include {% data variables.product.prodname_GH_code_security %} or {% data variables.product.prodname_GH_secret_protection %} features in a configuration. If you do, keep in mind that these features incur usage costs (or require {% data variables.product.prodname_GHAS %} licenses) when applied to private and internal repositories.
48
49
49
50
To start securing repositories in your organization with {% data variables.product.prodname_custom_security_configurations %}, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration).
Copy file name to clipboardExpand all lines: content/code-security/how-tos/scan-code-for-vulnerabilities/scan-from-the-command-line/advanced-setup-of-the-codeql-cli.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
@@ -112,6 +112,6 @@ When you have confirmed that a {% data variables.product.prodname_codeql %} data
112
112
gh api /repos/<owner>/<repo>/code-scanning/codeql/databases/<language> -H 'Accept: application/zip'> path/to/local/database.zip
113
113
```
114
114
115
-
For more information, see the documentation for the [Get {% data variables.product.prodname_codeql %} database endpoint](/rest/code-scanning?apiVersion=2022-11-28#get-a-codeql-database-for-a-repository).
115
+
For more information, see the documentation for the [Get {% data variables.product.prodname_codeql %} database endpoint](/rest/code-scanning/code-scanning#get-a-codeql-database-for-a-repository).
116
116
117
117
Before running an analysis with the {% data variables.product.prodname_codeql_cli %}, you must unzip the databases.
Copy file name to clipboardExpand all lines: content/code-security/how-tos/scan-code-for-vulnerabilities/scan-from-the-command-line/creating-database-bundle-for-troubleshooting.md
0 commit comments