Repo sync

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Docs changelog
 
+**20 January 2026**
+
+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. 
+
+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.
+
+The feature matrix is in public preview so that customers have time to gather and submit feedback to us. 
+
+<hr>
+
 **16 January 2026**
 
 The following new articles support the public preview release of Copilot Memory:

content/billing/how-tos/index.md

@@ -11,6 +11,7 @@ topics:
 children:
   - /set-up-payment
   - /manage-plan-and-licenses
+  - /set-up-budgets
   - /products
   - /manage-server-licenses
   - /pay-third-parties

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

@@ -19,6 +19,7 @@ redirect_from:
   - /billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages
   - /billing/managing-billing-for-your-products/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages
   - /billing/managing-your-billing/using-budgets-control-spending
+  - /billing/tutorials/set-up-budgets
 topics:
   - Billing
   - Enterprise
@@ -27,14 +28,14 @@ topics:
   - User account
 permissions: '{% data reusables.permissions.enhanced-billing-platform %}'
 shortTitle: Set up budgets
-contentType: tutorials
+contentType: how-tos
 ---
 
 Budgets help you track and control spending on different products. To learn more, see [AUTOTITLE](/billing/concepts/budgets-and-alerts).
 
-## Deciding on the type and scope for a budget
+## Plan your budget type and scope
 
-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.
+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.
 
 ![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)
 

content/billing/tutorials/index.md

@@ -11,10 +11,10 @@ topics:
 children:
   - /automate-usage-reporting
   - /soft-budgets
-  - /set-up-budgets
   - /control-costs-at-scale
   - /gather-insights
 contentType: tutorials
 redirect_from:
   - /billing/tutorials/estimate-actions-costs
 ---
+

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

@@ -36,7 +36,7 @@ If {% data variables.product.prodname_code_scanning %} finds a potential vulnera
 {% endif %}
 
 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
-[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert). For information about API endpoints, see [AUTOTITLE](/rest/code-scanning).
+[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert). For information about API endpoints, see [AUTOTITLE](/rest/code-scanning/code-scanning).
 
 {% ifversion fpt or ghec %}
 

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

@@ -73,7 +73,7 @@ There are dedicated views for each type of security alert. You can limit your an
 
 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 %}
 
-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).
+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.
 
 Security overview has multiple views that provide different ways to explore enablement and alert data.
 
@@ -97,49 +97,19 @@ You can find security overview on the **Security** tab for your enterprise. Each
 
 As with security overview for organizations, security overview for enterprises has multiple views that provide different ways to explore data.
 
-For information about permissions, see [Permission to view data in security overview](#permission-to-view-data-in-security-overview).
+## Access to data in security overview
 
-## Permission to view data in security overview
+What you can see in security overview depends on your role and permissions in the organization or enterprise.
 
-### Organization-level overview
+In general:
 
-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.
+* **Organization owners and security managers** can view security data across all repositories in their organization.
+* **Organization members** can view data only for repositories where they have access to security alerts.
+* **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.
 
-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.
+Security overview displays data only for repositories you have permission to view, and some views or actions may be limited based on your role.
 
-{% ifversion secret-risk-assessment %}
-
-> [!TIP] The Assessments view, which is not shown in the table below, is only available to organization owners and security managers.
-
-{% endif %}
-
-{% rowheaders %}
-
-| 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 %} |
-| `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 |
-| `read` or `triage` access for one or more repositories | No access | No access | No access |
-| 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 |
-| 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 |
-
-{% endrowheaders %}
-
-> [!NOTE]
-> 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.
-
-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).
-
-### Enterprise-level overview
-
-> [!NOTE]
-> 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).
-
-In the enterprise-level security overview, you can see data for all organizations where you are an **organization owner or security manager**.
-
-{% ifversion ghec %}
-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).
-{% endif %}
+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).
 
 ## Further reading
 

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

@@ -70,21 +70,21 @@ You can use the API to list and interact with security alerts, for example, gett
 
 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.
 
-For more information, see [{% data variables.product.prodname_dependabot %} alerts](/rest/dependabot/alerts#about-dependabot-alerts).
+For more information, see [AUTOTITLE](/rest/dependabot/alerts#about-dependabot-alerts).
 
 ### {% data variables.product.prodname_secret_scanning_caps %} alerts API
 
 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.
 
 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`.
 
-For more information, see [{% data variables.product.prodname_secret_scanning_caps %}](/rest/secret-scanning).
+For more information, see [AUTOTITLE](/rest/secret-scanning).
 
 ### {% data variables.product.prodname_code_scanning_caps %} alerts API
 
 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.
 
-For more information, see [{% data variables.product.prodname_code_scanning_caps %}](/rest/code-scanning).
+For more information, see [AUTOTITLE](/rest/code-scanning/code-scanning).
 
 ## Further reading
 

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

@@ -43,7 +43,8 @@ To start securing repositories in your organization with the {% data variables.p
 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:
 
 * Edit the enablement settings for different security features
-* Create several configurations for repositories with different security needs
-* 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
+* Create several configurations for repositories to reflect their different levels of visibility, risk tolerance, and impact
+
+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.
 
 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

@@ -112,6 +112,6 @@ When you have confirmed that a {% data variables.product.prodname_codeql %} data
 gh api /repos/<owner>/<repo>/code-scanning/codeql/databases/<language> -H 'Accept: application/zip' > path/to/local/database.zip
 ```
 
-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).
+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).
 
 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

@@ -1,6 +1,6 @@
 ---
 title: Creating CodeQL CLI database bundles
-shortTitle: Createting CodeQL CLI database bundles
+shortTitle: Creating CodeQL CLI database bundles
 intro: You can create a database bundle with {% data variables.product.prodname_codeql %} troubleshooting information.
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.codeql %}'

content/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/creating-a-custom-security-configuration.md

@@ -16,29 +16,19 @@ redirect_from:
 contentType: how-tos
 ---
 
-## About {% data variables.product.prodname_custom_security_configurations %}
+{% ifversion security-configurations-cloud %}
 
-{% ifversion fpt or ghec %}
+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 %}. For more information, see [AUTOTITLE](/code-security/concepts/security-at-scale/choosing-a-security-configuration-for-your-repositories).
 
-We recommend securing your organization with the {% data variables.product.prodname_github_security_configuration %}, then evaluating the security findings on your repositories before configuring {% data variables.product.prodname_custom_security_configurations %}. For more information, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-the-github-recommended-security-configuration-in-your-organization).
-
-{% endif %}
+{% else %}
 
 With {% data variables.product.prodname_custom_security_configurations %}, you can create collections of enablement settings for {% data variables.product.company_short %}'s security products to meet the specific security needs of your organization. For example, you can create a different {% data variables.product.prodname_custom_security_configuration %} for each group of repositories to reflect their different levels of visibility, risk tolerance, and impact.
 
-{% ifversion ghas-products %}
-
-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.
-
-{%- ifversion fpt or ghec %} 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.{% endif %} For more information, see [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security).
-
-{% endif %}
-
-{% ifversion ghes %}
-
 * Only features installed by a site administrator on your {% data variables.product.prodname_ghe_server %} instance will appear in the UI.
 * {% ifversion ghas-products %}Some features will only be visible if your organization or {% data variables.product.prodname_ghe_server %} instance has purchased the relevant {% data variables.product.prodname_GHAS %} product ({% data variables.product.prodname_GH_code_security %} or {% data variables.product.prodname_GH_secret_protection %}){% else %}{% data variables.product.prodname_GHAS %} features will only be visible if your organization or {% data variables.product.prodname_ghe_server %} instance holds a {% data variables.product.prodname_GHAS %} license{% endif %}.
-* Certain features, like {% data variables.product.prodname_dependabot_security_updates %} and {% data variables.product.prodname_code_scanning %} default setup, also require that {% data variables.product.prodname_actions %} is installed on the {% data variables.product.prodname_ghe_server %} instance.{% endif %}
+* Certain features, like {% data variables.product.prodname_dependabot_security_updates %} and {% data variables.product.prodname_code_scanning %} default setup, also require that {% data variables.product.prodname_actions %} is installed on the {% data variables.product.prodname_ghe_server %} instance.
+
+{% endif %}
 
 {% ifversion ghas-products %}