Skip to content

Commit f0c0a69

Browse files
authored
Merge pull request #42523 from github/repo-sync
Repo sync
2 parents 5935d63 + 4b03251 commit f0c0a69

File tree

24 files changed

+169
-101
lines changed

24 files changed

+169
-101
lines changed

CHANGELOG.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,15 @@
11
# Docs changelog
22

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+
313
**16 January 2026**
414

515
The following new articles support the public preview release of Copilot Memory:

content/billing/how-tos/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ topics:
1111
children:
1212
- /set-up-payment
1313
- /manage-plan-and-licenses
14+
- /set-up-budgets
1415
- /products
1516
- /manage-server-licenses
1617
- /pay-third-parties

content/billing/tutorials/set-up-budgets.md renamed to content/billing/how-tos/set-up-budgets.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ redirect_from:
1919
- /billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages
2020
- /billing/managing-billing-for-your-products/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages
2121
- /billing/managing-your-billing/using-budgets-control-spending
22+
- /billing/tutorials/set-up-budgets
2223
topics:
2324
- Billing
2425
- Enterprise
@@ -27,14 +28,14 @@ topics:
2728
- User account
2829
permissions: '{% data reusables.permissions.enhanced-billing-platform %}'
2930
shortTitle: Set up budgets
30-
contentType: tutorials
31+
contentType: how-tos
3132
---
3233

3334
Budgets help you track and control spending on different products. To learn more, see [AUTOTITLE](/billing/concepts/budgets-and-alerts).
3435

35-
## Deciding on the type and scope for a budget
36+
## Plan your budget type and scope
3637

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.
3839

3940
![Screenshot of budgets for "octo-org": "Actions" budget is $50 and "Actions Linux 96-core" budget is $100. All the "Actions" budget has been used.](/assets/images/help/billing/org-budget-example.png)
4041

content/billing/tutorials/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,10 @@ topics:
1111
children:
1212
- /automate-usage-reporting
1313
- /soft-budgets
14-
- /set-up-budgets
1514
- /control-costs-at-scale
1615
- /gather-insights
1716
contentType: tutorials
1817
redirect_from:
1918
- /billing/tutorials/estimate-actions-costs
2019
---
20+

content/code-security/concepts/code-scanning/about-code-scanning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ If {% data variables.product.prodname_code_scanning %} finds a potential vulnera
3636
{% endif %}
3737

3838
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).
4040

4141
{% ifversion fpt or ghec %}
4242

content/code-security/concepts/security-at-scale/about-security-overview.md

Lines changed: 9 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ There are dedicated views for each type of security alert. You can limit your an
7373

7474
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 %}
7575

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.
7777

7878
Security overview has multiple views that provide different ways to explore enablement and alert data.
7979

@@ -97,49 +97,19 @@ You can find security overview on the **Security** tab for your enterprise. Each
9797

9898
As with security overview for organizations, security overview for enterprises has multiple views that provide different ways to explore data.
9999

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
101101

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.
103103

104-
### Organization-level overview
104+
In general:
105105

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.
107109

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.
109111

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 |
119-
|--------------------|-------------|---------------------|---------|
120-
| `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).
143113

144114
## Further reading
145115

content/code-security/concepts/security-at-scale/auditing-security-alerts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,21 +70,21 @@ You can use the API to list and interact with security alerts, for example, gett
7070

7171
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.
7272

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).
7474

7575
### {% data variables.product.prodname_secret_scanning_caps %} alerts API
7676

7777
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.
7878

7979
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`.
8080

81-
For more information, see [{% data variables.product.prodname_secret_scanning_caps %}](/rest/secret-scanning).
81+
For more information, see [AUTOTITLE](/rest/secret-scanning).
8282

8383
### {% data variables.product.prodname_code_scanning_caps %} alerts API
8484

8585
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.
8686

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).
8888

8989
## Further reading
9090

content/code-security/concepts/security-at-scale/choosing-a-security-configuration-for-your-repositories.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,8 @@ To start securing repositories in your organization with the {% data variables.p
4343
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:
4444

4545
* 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.
4849

4950
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).

content/code-security/how-tos/scan-code-for-vulnerabilities/scan-from-the-command-line/advanced-setup-of-the-codeql-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,6 @@ When you have confirmed that a {% data variables.product.prodname_codeql %} data
112112
gh api /repos/<owner>/<repo>/code-scanning/codeql/databases/<language> -H 'Accept: application/zip' > path/to/local/database.zip
113113
```
114114

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).
116116

117117
Before running an analysis with the {% data variables.product.prodname_codeql_cli %}, you must unzip the databases.

content/code-security/how-tos/scan-code-for-vulnerabilities/scan-from-the-command-line/creating-database-bundle-for-troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Creating CodeQL CLI database bundles
3-
shortTitle: Createting CodeQL CLI database bundles
3+
shortTitle: Creating CodeQL CLI database bundles
44
intro: You can create a database bundle with {% data variables.product.prodname_codeql %} troubleshooting information.
55
allowTitleToDifferFromFilename: true
66
product: '{% data reusables.gated-features.codeql %}'

0 commit comments

Comments
 (0)