Merge pull request #44113 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/headless-tests.yml

@@ -59,6 +59,7 @@ jobs:
           PLAYWRIGHT_WORKERS: ${{ fromJSON('[1, 4]')[github.repository == 'github/docs-internal'] }}
           # workaround for https://github.com/nodejs/node/issues/59364 as of 22.18.0
           NODE_OPTIONS: '--no-experimental-strip-types'
+          PLAYWRIGHT_TIMEOUT: ${{ matrix.node == 'playwright-a11y' && '60000' || '' }}
 
         # Run playwright rendering tests and a11y tests (axe scans) as distinct checks
         # so that we can run them without blocking merges until we can be confident

content/admin/data-residency/github-copilot-with-data-residency.md

@@ -54,7 +54,6 @@ The models available for {% data variables.product.prodname_copilot_short %} var
 * GPT-5.2
 * GPT-5.4
 * Claude Haiku 4.5
-* Claude Sonnet 4
 * Claude Sonnet 4.5
 * Claude Opus 4.5
 * Claude Sonnet 4.6

content/copilot/concepts/agents/copilot-cli/about-cli-plugins.md

@@ -59,6 +59,8 @@ Examples of marketplaces include:
 
 For more about adding marketplaces and installing plugins from them, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing).
 
+Enterprise administrators can also define plugin standards that apply across the enterprise, including specifying additional marketplaces and plugins that are automatically installed for all {% data variables.copilot.copilot_cli_short %} users. See [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-enterprise-plugin-standards).
+
 ## Plugins compared with manual configuration
 
 Any functionality that you could add with a plugin, you could also add by configuring {% data variables.copilot.copilot_cli_short %} manually—for example, by adding custom agent profiles or MCP servers. However, plugins provide several advantages over manual configuration:

content/copilot/concepts/agents/copilot-cli/about-enterprise-plugin-standards.md

@@ -0,0 +1,42 @@
+---
+title: About enterprise-managed plugin standards for {% data variables.copilot.copilot_cli_short %}
+shortTitle: Enterprise plugin standards
+allowTitleToDifferFromFilename: true
+intro: 'Enterprise administrators can centrally define plugin policies for {% data variables.copilot.copilot_cli_short %}, ensuring consistent plugin availability across their enterprise.'
+versions:
+  feature: copilot
+contentType: concepts
+category:
+  - Learn about Copilot # Copilot discovery page
+  - Learn about Copilot CLI # Copilot CLI bespoke page
+docsTeamMetrics:
+  - copilot-cli
+---
+
+> [!NOTE] This feature is in {% data variables.release-phases.public_preview %} and subject to change.
+
+Enterprise-managed plugin standards allow administrators to **define and enforce policies for plugin availability** in {% data variables.copilot.copilot_cli_short %} across their enterprise. By configuring a `settings.json` file in the enterprise's `.github-private` repository, administrators can specify which plugin marketplaces are available to users and which plugins are automatically installed for all enterprise users.
+
+## How plugin standards work
+
+Enterprise plugin standards use a configuration file stored in your enterprise's `.github-private` repository. The configuration is defined in a `settings.json` file at the following path: `.github/copilot/settings.json`.
+
+For plugin standards, the file can define:
+
+* **Known marketplaces**. Plugin marketplaces that are available to users for browsing and installing plugins.
+* **Default-enabled plugins**. Specific plugins that are automatically installed for all enterprise users when they authenticate with the CLI.
+
+When a user signs in to {% data variables.copilot.copilot_cli_short %}, the client queries an API endpoint that reads the `settings.json` from the enterprise's `.github-private` repository. The policies defined in the file are then applied to the user's CLI session.
+
+## Why use enterprise-managed plugin standards
+
+Enterprise-managed plugin standards help administrators address several common challenges:
+
+* **Consistency across clients**. Ensure that all developers using {% data variables.copilot.copilot_cli_short %} with an enterprise-assigned {% data variables.product.prodname_copilot_short %} license have access to the same plugins and marketplaces.
+* **Centralized governance**. Manage plugin availability from a single configuration file, rather than relying on individual developers to install the correct plugins.
+* **Version-controlled policies**. Because the configuration lives in a Git repository, all changes to plugin standards are tracked, auditable, and reviewable through pull requests.
+* **Reduced onboarding friction**. New developers automatically receive the enterprise's standard plugins when they authenticate, without any manual setup.
+
+## Next step
+
+To configure enterprise plugin standards for {% data variables.copilot.copilot_cli_short %}, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-plugin-standards).

content/copilot/concepts/agents/copilot-cli/index.md

@@ -12,6 +12,7 @@ children:
   - /about-remote-control
   - /about-custom-agents
   - /about-cli-plugins
+  - /about-enterprise-plugin-standards
   - /autopilot
   - /fleet
   - /research

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-plugin-standards.md

@@ -0,0 +1,42 @@
+---
+title: Configuring enterprise plugin standards for {% data variables.copilot.copilot_cli_short %}
+shortTitle: Configure plugin standards
+allowTitleToDifferFromFilename: true
+intro: 'Configure enterprise plugin standards by defining a `settings.json` file in your enterprise''s `.github-private` repository.'
+permissions: Enterprise owners
+versions:
+  feature: copilot
+contentType: how-tos
+category:
+  - Configure Copilot
+  - Manage Copilot for a team
+---
+
+> [!NOTE] This feature is in {% data variables.release-phases.public_preview %} and subject to change.
+
+1. In your enterprise's `.github-private` repository, navigate to the `.github/copilot/` directory. If you don't have a `.github-private` repository yet, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents).
+1. Create or edit the `settings.json` file at `.github/copilot/settings.json`.
+1. Add your plugin policy configuration to the file. The `settings.json` file supports the following top-level properties:
+
+   ```json copy
+   {
+     "extraKnownMarketplaces": {
+       "MARKETPLACE-NAME": {
+         "source": {
+           "source": "github",
+           "repo": "OWNER/REPO"
+         }
+       }
+     },
+     "enabledPlugins": {
+       "PLUGIN-NAME@MARKETPLACE-NAME": true
+     }
+   }
+   ```
+
+   * `extraKnownMarketplaces`: Defines additional plugin marketplaces available to CLI users. Each entry is a named marketplace object containing a `source` property that specifies the provider (`"github"`) and the repository in `OWNER/REPO` format.
+   * `enabledPlugins`: Defines plugins that are automatically installed for all enterprise users. Each entry uses the format `PLUGIN-NAME@MARKETPLACE-NAME` as the key, with a boolean value of `true` to enable the plugin.
+
+1. Commit and push your changes to the default branch of the `.github-private` repository.
+
+Once the configuration is committed, enterprise users will see the specified marketplaces and pre-installed plugins the next time they authenticate with {% data variables.copilot.copilot_cli_short %}.

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/index.md

@@ -6,6 +6,7 @@ versions:
   feature: copilot
 children:
   - /prepare-for-custom-agents
+  - /configure-enterprise-plugin-standards
   - /monitor-agentic-activity
   - /enable-copilot-cloud-agent
   - /block-copilot-cloud-agent

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/prepare-for-custom-agents.md

@@ -13,6 +13,8 @@ category:
 
 Enterprise-level {% data variables.copilot.custom_agents_short %} are defined in a specific repository within an organization in your enterprise. Before you can create and use {% data variables.copilot.custom_agents_short %}, you need to create this repository and configure the relevant enterprise settings.
 
+The same `.github-private` repository can also be used to configure enterprise plugin standards for {% data variables.copilot.copilot_cli_short %}. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-plugin-standards).
+
 ## Creating a repository for your {% data variables.copilot.custom_agents_short %}
 
 1. Choose an organization in your enterprise to own the repository containing your enterprise-level {% data variables.copilot.custom_agents_short %}.

content/copilot/reference/ai-models/model-hosting.md

@@ -57,7 +57,6 @@ Used for:
 * {% data variables.copilot.copilot_claude_opus_46 %}
 * {% data variables.copilot.copilot_claude_opus_46_fast %}
 * {% data variables.copilot.copilot_claude_opus_47 %}
-* {% data variables.copilot.copilot_claude_sonnet_40 %}
 * {% data variables.copilot.copilot_claude_sonnet_46 %}
 
 These models are hosted by Amazon Web Services, Anthropic PBC, and Google Cloud Platform. {% data variables.product.github %} has provider agreements in place to ensure data is not used for training. Additional details for each provider are included below:

data/reusables/copilot/model-compliance/us-models.md

@@ -6,7 +6,6 @@
 * GPT-5.2-Codex
 * GPT-5.3-Codex
 * Claude Haiku 4.5
-* Claude Sonnet 4
 * Claude Sonnet 4.5
 * Claude Opus 4.5
 * Claude Sonnet 4.6