Merge pull request #44703 from github/repo-sync

docs-bot · web-flow · commit f01ab76d7297 · 2026-06-12T08:34:44.000-07:00
Repo sync
diff --git a/content/admin/monitoring-and-managing-your-instance/additional-nodes/configuring-additional-nodes.md b/content/admin/monitoring-and-managing-your-instance/additional-nodes/configuring-additional-nodes.md
@@ -10,10 +10,6 @@ category:
   - Scale your instance
 ---
 
-> [!NOTE]
-> The ability to add additional compute nodes to HA is in {% data variables.release-phases.public_preview %} and subject to change. During the preview, please share any feedback with your customer success team.
-
-
 For {% data variables.product.prodname_ghe_server %} customers looking to scale horizontally, migrating to and operating a cluster is an option, but is resource-intensive and time-consuming. As an alternative, we recommend adding nodes to an HA configuration.
 
 The terms "additional node" and "stateless node" are used interchangeably throughout this article. Stateless nodes can only be added to HA deployments that contain at least one replica.
@@ -59,7 +55,7 @@ ghe-cluster-balance rebalance --yes
 
 The `ghe-config-apply` command is a requirement to add stateless nodes.
 
-For the public preview, we have not specifically tested for downtime, and it's not clear if a maintenance window is required.
+We recommend a maintenance window to add stateless nodes.
 
 ## Removing an additional node
 
@@ -71,7 +67,7 @@ ghe-config-apply
 
 The `ghe-config-apply` command is a requirement to remove stateless nodes.
 
-For the public preview, we have not specifically tested for downtime, and it's not clear if a maintenance window is required.
+We recommend a maintenance window to remove stateless nodes.
 
 ## Reprovisioning a node that previously hosted {% data variables.product.prodname_ghe_server %}
 
diff --git a/content/billing/reference/supported-payment-methods.md b/content/billing/reference/supported-payment-methods.md
@@ -43,7 +43,8 @@ The following Azure subscription types cannot be used as a payment method for {%
 | `AzureForStudents_2018-01-01` | MS-AZR-0170P |
 | `DreamSpark_2015-02-01` | MS-AZR-0144P |
 | `AzurePass_2014-09-01` | MS-AZR-0120P, MS-AZR-0122P–MS-AZR-0125P, MS-AZR-0128P–MS-AZR-0130P |
-| `PayAsYouGo_2014-09-01` | MS-AZR-0017G |
+| `PayAsYouGo_2014-09-01` | MS-AZR-0001P, MS-AZR-0002P, MS-AZR-0003P, MS-AZR-0006P, MS-AZR-0008P, MS-AZR-0010P, MS-AZR-0011P, MS-AZR-0018P, MS-AZR-0019P, MS-AZR-0030P, MS-AZR-0044P, MS-AZR-0046P, MS-AZR-0048P, MS-AZR-0050P |
+| `MSDN_2014-09-01` | MS-AZR-0029P, MS-AZR-0059P, MS-AZR-0062P, MS-AZR-0063P |
 
 {% ifversion fpt or ghec %}
 
diff --git a/content/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configure-code-scanning.md b/content/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configure-code-scanning.md
@@ -77,7 +77,7 @@ Your repository is eligible for default setup for {% data variables.product.prod
 1. Optionally, to view your default setup configuration after enablement, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} View {% data variables.product.prodname_codeql %} configuration**.
 
 > [!NOTE]
-> If no pushes and pull requests have occurred in a repository with default setup enabled for 6 months, the weekly schedule will be disabled to save your {% data variables.product.prodname_actions %} minutes.
+> If no pushes and pull requests have occurred in a repository with default setup enabled for 6 months, the weekly schedule will be disabled to save your {% data variables.product.prodname_actions %} minutes.{% ifversion code-scanning-inactive-repos %} Organization owners can enable monthly scans of inactive repositories. For more information, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/configuring-global-security-settings-for-your-organization#continuing-scans-on-inactive-repositories).{% endif %}
 
 {% ifversion fpt or ghec %}
 
diff --git a/content/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/edit-default-setup.md b/content/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/edit-default-setup.md
@@ -83,6 +83,19 @@ For more information about {% data variables.product.prodname_codeql %} model pa
 
 1. The model packs will be automatically detected and used when {% data variables.product.prodname_code_scanning %} runs on any repository in the organization with default setup enabled.
 
+{% ifversion code-scanning-inactive-repos %}
+
+## Continuing scans on inactive repositories
+
+{% data reusables.code-scanning.inactive-repos-scan %} You can override this behavior in an organization, though the scan period is not configurable.
+
+{% data reusables.profile.access_org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.security-configurations.display-global-settings %}
+1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, enable the **Keep scheduled scans running every 30 days for inactive repositories** setting.
+
+{% endif %}
+
 ## Further customization
 
 If you need to change any other aspects of your {% data variables.product.prodname_code_scanning %} configuration, consider configuring advanced setup. See [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
diff --git a/content/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/code-scanning-at-scale.md b/content/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/code-scanning-at-scale.md
@@ -33,9 +33,9 @@ A repository must meet all the following criteria to be eligible for default set
 
 You can enable default setup for all eligible repositories in your organization. For more information, see [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale).
 
-### Extending {% data variables.product.prodname_codeql %} coverage in default setup
+### Configuring default setup features
 
-Through your organization's security settings page, you can extend coverage in default setup using model packs for all eligible repositories in your organization. For more information, see [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup#extending-coverage-for-all-repositories-in-an-organization).
+Through your organization's security settings page, you can customize default setup for all eligible repositories, such as extending coverage using model packs. See [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup).
 
 ## Configuring default setup for a subset of repositories in an organization
 
diff --git a/content/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings.md b/content/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings.md
@@ -105,6 +105,9 @@ You can customize several {% data variables.product.prodname_global_settings %}
 {% ifversion code-scanning-autofix %}* [Enabling {% data variables.copilot.copilot_autofix_short %} for {% data variables.product.prodname_codeql %}](#enabling-copilot-autofix-for-codeql){% endif %}
 * [Recommending the extended query suite for default setup](#recommending-the-extended-query-suite-for-default-setup)
 * [Expanding {% data variables.product.prodname_codeql %} analysis](#expanding-codeql-analysis)
+{%- ifversion code-scanning-inactive-repos %}
+* [Continuing scans on inactive repositories](#continuing-scans-on-inactive-repositories)
+{%- endif %}
 
 {% endif %}
 
@@ -124,6 +127,14 @@ You can select **{% data variables.copilot.copilot_autofix_short %}** to enable
 
 You can expand {% data variables.product.prodname_codeql %} analysis coverage for all repositories in your organization that use default setup by configuring {% data variables.product.prodname_codeql %} model packs. Model packs extend the {% data variables.product.prodname_codeql %} analysis to recognize additional frameworks and libraries that are not included in the standard {% data variables.product.prodname_codeql %} libraries. This global configuration applies to repositories using default setup and allows you to specify model packs published via the container registry. For more information, see [AUTOTITLE](/code-security/how-tos/scan-code-for-vulnerabilities/manage-your-configuration/editing-your-configuration-of-default-setup#extending-coverage-for-all-repositories-in-an-organization).
 
+{% ifversion code-scanning-inactive-repos %}
+
+### Continuing scans on inactive repositories
+
+{% data reusables.code-scanning.inactive-repos-scan %} You can select **Keep scheduled scans running every 30 days for inactive repositories** to override this behavior in an organization. The scan period is not configurable.
+
+{% endif %}
+
 ## Configuring global {% data variables.product.prodname_secret_scanning %} settings
 
 {% data reusables.security-configurations.secret-scanning-security-configs-summary %}
diff --git a/content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md b/content/copilot/how-tos/copilot-cli/use-copilot-cli/overview.md
@@ -283,6 +283,18 @@ You can run {% data variables.copilot.copilot_cli_short %} sessions inside a san
 
 Press <kbd>Ctrl</kbd>+<kbd>T</kbd> to show or hide the model's reasoning process while it generates a response. This setting persists across sessions, allowing you to observe how {% data variables.product.prodname_copilot_short %} works through complex problems.
 
+### Configure settings
+
+You can view and change {% data variables.copilot.copilot_cli_short %} settings using the `/settings` slash command.
+
+* Run `/settings` to open an interactive settings dialog, where you can search for a setting by name and edit it.
+* Run `/settings KEY VALUE` to set a setting inline, where KEY is the name of the setting and VALUE is the value you want to set. This also works in scripts and in programmatic sessions started with `-p`.
+* Run `/settings reset KEY` to restore a setting to its default value.
+
+Some settings, such as the color mode, take effect immediately when you save them.
+
+For the full list of available settings, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-config-dir-reference#configuration-file-settings).
+
 ## Find out more
 
 For a complete list of the command line options and slash commands that you can use with {% data variables.copilot.copilot_cli_short %}, do one of the following:
diff --git a/content/copilot/reference/copilot-billing/request-based-billing-legacy/monitor-premium-requests.md b/content/copilot/reference/copilot-billing/request-based-billing-legacy/monitor-premium-requests.md
@@ -37,9 +37,6 @@ If you reach your limit for premium requests, you will be notified with a messag
 
 ### Viewing usage in your IDE
 
-> [!IMPORTANT]
-> **Starting April 20, 2026**, {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, and student plans have tighter usage limits: Session limits and weekly (7 day) limits. {% data variables.product.prodname_vscode_shortname %} and {% data variables.copilot.copilot_cli %} both display your available usage when you are approaching a limit. See [AUTOTITLE](/copilot/concepts/usage-limits).
-
 If you're using {% data variables.product.prodname_copilot_short %} in an editor, you can view your usage directly in the editor. For example, in {% data variables.product.prodname_vscode %}, you can view information about features included in your plan, your progress towards any limits on your plan, and the date your allowance resets.
 
 You can access usage information in the following IDEs.
diff --git a/content/copilot/reference/copilot-cli-reference/cli-command-reference.md b/content/copilot/reference/copilot-cli-reference/cli-command-reference.md
@@ -244,6 +244,7 @@ Holding <kbd>↑</kbd> or <kbd>↓</kbd> accelerates scrolling after the first 1
 | `/sandbox [enable\|disable]`                        | Configure shell command sandboxing. |
 | `/search [QUERY]`, `/find [QUERY]`                  | Search the conversation timeline. {% data reusables.copilot.experimental %} |
 | `/session [info\|checkpoints [n]\|files\|plan\|rename [NAME]\|cleanup\|prune\|delete [ID]\|delete-all]`, `/sessions [info\|checkpoints [n]\|files\|plan\|rename [NAME]\|cleanup\|prune\|delete [ID]\|delete-all]`  | Show session information and manage sessions. The `info` subcommand shows session details including the session link (when available). Subcommands: `info`, `checkpoints`, `files`, `plan`, `rename`, `cleanup`, `prune`, `delete`, `delete-all`. |
+| `/settings [show\|[KEY VALUE]\|reset KEY]`  | Open the settings dialog, set a setting inline with a KEY and VALUE, or reset a setting to its default. See [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-config-dir-reference#configuration-file-settings). |
 | `/share [file\|html\|gist] [session\|research] [PATH]`, `/export [file\|html\|gist] [session\|research] [PATH]` | Share the session to a Markdown file, interactive HTML file, or {% data variables.product.github %} gist. |
 | `/skills [list\|info\|add\|remove\|reload] [ARGS...]`   | Manage skills for enhanced capabilities. See [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/create-skills). |
 | `/statusline`, `/footer`                            | Configure which items appear in the status line. |
diff --git a/content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md b/content/copilot/reference/copilot-cli-reference/cli-config-dir-reference.md
@@ -50,7 +50,7 @@ The following files are designed to be edited by you directly, or managed throug
 
 ### `settings.json`
 
-This is the primary configuration file for {% data variables.copilot.copilot_cli_short %}. You can edit it directly in a text editor, or use interactive commands like `/model` and `/theme` to change specific values from within a session. The file supports JSON with comments (JSONC).
+This is the primary configuration file for {% data variables.copilot.copilot_cli_short %}. Within a session, you can use the interactive `/settings` command to change specific values, or run `/settings KEY VALUE` to set a single value, or edit the file directly in a text editor. The file supports JSON with comments (JSONC).
 
 > [!NOTE]
 > User-editable settings were originally stored in `config.json`. They have been moved to `settings.json`. Any user settings present in `config.json` on startup are automatically migrated to `settings.json`.
@@ -204,7 +204,7 @@ Settings cascade from user to repository to local, with more specific scopes ove
 
 ### User settings (`~/.copilot/settings.json`)
 
-These settings apply across all your sessions and repositories. You can edit this file directly, or use slash commands to update individual values.
+These settings apply across all your sessions and repositories. You can use the `/settings` slash command to run an interactive dialog, or use specific slash commands to update individual values, or edit this file directly.
 
 | Key | Type | Default | Description |
 |-----|------|---------|-------------|
diff --git a/content/copilot/tutorials/roll-out-at-scale/govern-at-scale/resources-for-approval.md b/content/copilot/tutorials/roll-out-at-scale/govern-at-scale/resources-for-approval.md
@@ -53,6 +53,7 @@ These teams need to know how {% data variables.product.prodname_copilot_short %}
 
 * The allowlist required for a firewall or proxy to ensure {% data variables.product.prodname_copilot_short %} works as expected. See [AUTOTITLE](/copilot/reference/copilot-allowlist-reference).
 * The network protocol that {% data variables.product.prodname_copilot_short %} operates on by default, and your company's options for routing traffic through a proxy server and intercepting traffic. See [AUTOTITLE](/copilot/concepts/network-settings).
+* The option to use {% data variables.product.prodname_copilot_short %} in air-gapped environments by bringing your own API keys in {% data variables.product.prodname_vscode_shortname %} or {% data variables.copilot.copilot_cli_short %}. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/use-your-own-api-keys).
 * The clients where users will be using {% data variables.product.prodname_copilot_short %}.
   * Your enterprise can enable or disable {% data variables.product.prodname_copilot_short %} in IDEs, on {% data variables.product.prodname_mobile %}, in the CLI, and on the {% data variables.product.github %} website.
   * If your company distributes approved software for users, IT teams may need to approve the supported versions of IDEs. See [AUTOTITLE](/copilot/reference/copilot-feature-matrix).
diff --git a/content/rest/billing/budgets.md b/content/rest/billing/budgets.md
@@ -12,4 +12,25 @@ category:
   - Administer enterprises and billing
 ---
 
+> [!IMPORTANT]
+> The request body schema below is missing a required field. When `budget_scope` is `user`, you must also include a `user` field set to the {% data variables.product.company_short %} username the budget applies to. If you omit this field, the API returns `HTTP 400: Missing required fields: budget_entity_name`. For user-scoped budgets, `budget_entity_name` can be an empty string.
+
+The following example creates a user-scoped budget that limits a single user's monthly {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %} to $30 USD:
+
+```json
+{
+  "budget_amount": 30,
+  "prevent_further_usage": true,
+  "budget_scope": "user",
+  "budget_entity_name": "",
+  "budget_type": "BundlePricing",
+  "budget_product_sku": "ai_credits",
+  "budget_alerting": {
+    "will_alert": false,
+    "alert_recipients": []
+  },
+  "user": "USERNAME"
+}
+```
+
 <!-- Content after this section is automatically generated -->
diff --git a/data/features/code-scanning-inactive-repos.yml b/data/features/code-scanning-inactive-repos.yml
@@ -0,0 +1,5 @@
+# Ref: 22601
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.22'
diff --git a/data/release-notes/enterprise-server/3-18/10.yml b/data/release-notes/enterprise-server/3-18/10.yml
@@ -68,8 +68,6 @@ sections:
       When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages.
     - |
       The setting to define private registries at the organization level for code scanning is only available if dependabot is also enabled for the instance.
-    - |
-      Custom NTP settings are removed during the upgrade process.
     - |
       When applying an enterprise security configuration to all repositories (for example, enabling Secret Scanning or Code Scanning across all repositories), the system immediately enqueues enablement jobs for every organization in the enterprise simultaneously. For enterprises with a large number of repositories, this can result in significant system load and potential performance degradation. If you manage a large enterprise with many organizations and repositories, we recommend applying security configurations at the organization level rather than at the enterprise level in the UI. This allows you to enable security features incrementally and monitor system performance as you roll out changes.
     - |
diff --git a/data/release-notes/enterprise-server/3-18/4.yml b/data/release-notes/enterprise-server/3-18/4.yml
@@ -92,5 +92,3 @@ sections:
       When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages.
     - |
       The setting to define private registries at the organization level for code scanning is only available if Dependabot is enabled for the instance.
-    - |
-      Custom NTP settings are removed during the upgrade process.
diff --git a/data/release-notes/enterprise-server/3-18/5.yml b/data/release-notes/enterprise-server/3-18/5.yml
@@ -94,7 +94,5 @@ sections:
       When publishing npm packages in a workflow after restoring from a backup to GitHub Enterprise Server 3.13.5.gm4 or 3.14.2.gm3, you may encounter a `401 Unauthorized` error from the GitHub Packages service. This can happen if the restore is from an N-1 or N-2 version and the workflow targets the npm endpoint on the backup instance. To avoid this issue, ensure the access token is valid and includes the correct scopes for publishing to GitHub Packages.
     - |
       The setting to define private registries at the organization level for code scanning is only available if dependabot is also enabled for the instance.
-    - |
-      Custom NTP settings are removed during the upgrade process.
     - |
       When applying an enterprise security configuration to all repositories (for example, enabling Secret Scanning or Code Scanning across all repositories), the system immediately enqueues enablement jobs for every organization in the enterprise simultaneously. For enterprises with a large number of repositories, this can result in significant system load and potential performance degradation. If you manage a large enterprise with many organizations and repositories, we recommend applying security configurations at the organization level rather than at the enterprise level in the UI. This allows you to enable security features incrementally and monitor system performance as you roll out changes.
diff --git a/data/release-notes/enterprise-server/3-18/6.yml b/data/release-notes/enterprise-server/3-18/6.yml
diff --git a/data/release-notes/enterprise-server/3-18/7.yml b/data/release-notes/enterprise-server/3-18/7.yml
diff --git a/data/release-notes/enterprise-server/3-18/8.yml b/data/release-notes/enterprise-server/3-18/8.yml
diff --git a/data/release-notes/enterprise-server/3-18/9.yml b/data/release-notes/enterprise-server/3-18/9.yml
diff --git a/data/release-notes/enterprise-server/3-19/0.yml b/data/release-notes/enterprise-server/3-19/0.yml
diff --git a/data/reusables/code-scanning/inactive-repos-scan.md b/data/reusables/code-scanning/inactive-repos-scan.md
diff --git a/data/reusables/copilot/byok-why.md b/data/reusables/copilot/byok-why.md
diff --git a/data/reusables/dependabot/dependabot-updates-supported-versioning-tags.md b/data/reusables/dependabot/dependabot-updates-supported-versioning-tags.md
