Merge branch 'main' into patch-4

Author: Sharra-writes

content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md

@@ -58,6 +58,7 @@ Let's compare some aspects of each solution:
 | Each step is logged in real-time | Logged as one step even if it contains multiple steps |
 | Can connect a maximum of ten levels of workflows | Can be nested to have up to 10 composite actions in one workflow |
 | Can use secrets | Cannot use secrets |
+| Cannot be published to the [marketplace](https://github.com/marketplace?type=actions) | Can be published to the [marketplace](https://github.com/marketplace?type=actions) |
 
 ## Workflow templates
 

content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md

@@ -234,7 +234,7 @@ on:
   gollum
 ```
 
-## image_version_ready
+## `image_version`
 
 | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
 |----------------------| -------------- | ------------ | -------------|

content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md

@@ -171,7 +171,7 @@ Supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`.
 
 ## `cooldown` {% octicon "versions" aria-label="Version updates" height="24" %}
 
-Defines a **cooldown period** for dependency updates, allowing updates to be delayed for a configurable number of days. The `coooldown` option is only available for _version_ updates, not _security_ updates.
+Defines a **cooldown period** for dependency updates, allowing updates to be delayed for a configurable number of days. The `cooldown` option is only available for _version_ updates, not _security_ updates.
 
 This feature enables users to customize how often {% data variables.product.prodname_dependabot %} generates new version updates, offering greater control over update frequency. For examples, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/optimizing-pr-creation-version-updates#setting-up-a-cooldown-period-for-dependency-updates).
 

content/copilot/concepts/agents/code-review.md

@@ -61,15 +61,13 @@ In the event that {% data variables.product.prodname_actions %} is unavailable o
 * Xcode
 * JetBrains IDEs
 
-{% data variables.copilot.copilot_code-review_short %} is—with one exception—a premium feature, available with the {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, {% data variables.copilot.copilot_business_short %}, and {% data variables.copilot.copilot_enterprise_short %} plans. See [Copilot plans](https://github.com/features/copilot/plans?ref_product=copilot&ref_type=purchase&ref_style=text&utm_source=docs-signup-copilot&utm_medium=docs&utm_campaign=universe25post).
-
-The exception is the review of a selection of code within a file in {% data variables.product.prodname_vscode %}. This is a standard feature available to all {% data variables.product.prodname_copilot_short %} users in {% data variables.product.prodname_vscode_shortname %}.
+{% data variables.copilot.copilot_code-review_short %} is a premium feature, available with the {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, {% data variables.copilot.copilot_business_short %}, and {% data variables.copilot.copilot_enterprise_short %} plans. See [Copilot plans](https://github.com/features/copilot/plans?ref_product=copilot&ref_type=purchase&ref_style=text&utm_source=docs-signup-copilot&utm_medium=docs&utm_campaign=universe25post).
 
 If you receive {% data variables.product.prodname_copilot_short %} from an organization then, to be able to request a pull request review from {% data variables.product.prodname_copilot_short %} on {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_mobile %}, the **{% data variables.copilot.copilot_code-review_short %}** option must be enabled in the {% data variables.product.prodname_copilot_short %} policy settings for the organization. See [AUTOTITLE](/copilot/how-tos/administer/organizations/managing-policies-for-copilot-in-your-organization).
 
 ## Code review monthly quota
 
-Each time {% data variables.product.prodname_copilot_short %} reviews a pull request, or reviews files in your IDE that contain uncommitted changes, your monthly quota of Copilot premium requests is reduced by one. Code review for currently selected text in {% data variables.product.prodname_vscode_shortname %} does not consume a premium request. For information about premium requests, see [AUTOTITLE](/copilot/managing-copilot/monitoring-usage-and-entitlements/about-premium-requests).
+Each time {% data variables.product.prodname_copilot_short %} reviews a pull request, or reviews code in your IDE, your monthly quota of Copilot premium requests is reduced by one.
 
 If a repository is configured to automatically request a code review from {% data variables.product.prodname_copilot_short %} for all new pull requests, the premium request usage is applied to the quota of the pull request author. If a pull request is created by {% data variables.product.prodname_actions %} or by a bot, the usage will apply to the user who triggered the workflow (if identifiable), or to a designated billing owner.
 
@@ -81,17 +79,6 @@ When you reach your monthly quota you will not be able to get a code review from
 
 {% data reusables.copilot.ccr-model-settings %}
 
-## {% data variables.copilot.copilot_code-review_short %} in {% data variables.product.prodname_vscode %}
-
-{% data variables.copilot.copilot_code-review_short %} in {% data variables.product.prodname_vscode %} supports two types of review:
-
-* **Review selection:**
-  * Highlight code and ask for an initial review.
-  * Standard {% data variables.product.prodname_copilot_short %} feature. No premium requests used.
-* **Review changes:**
-  * Request a deeper review of all of your uncommitted changes.
-  * Premium feature. Uses one premium request from your monthly quota per review.
-
 ## Providing instructions for {% data variables.product.prodname_copilot_short %} code reviews
 
 You can tailor the reviews that {% data variables.product.prodname_copilot_short %} generates by providing custom instructions. This helps {% data variables.product.prodname_copilot_short %} to review the code in a way that matches your team's coding standards, tools, and practices. See [AUTOTITLE](/copilot/how-tos/configure-custom-instructions/add-repository-instructions?tool=webui) and [AUTOTITLE](/copilot/how-tos/configure-custom-instructions/add-organization-instructions).

content/copilot/concepts/index.md

@@ -19,6 +19,7 @@ children:
   - /billing
   - /about-enterprise-accounts-for-copilot-business
   - /policies
+  - /mcp-management
   - /network-settings
   - /copilot-metrics
 contentType: concepts

content/copilot/concepts/mcp-management.md

@@ -0,0 +1,51 @@
+---
+title: MCP server usage in your company
+shortTitle: MCP management
+intro: 'You can manage MCP server usage to provide your developers with valuable tools while maintaining security and compliance.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+contentType: concepts
+---
+
+You can manage Model Context Protocol (MCP) server usage in your organization or enterprise by configuring a series of MCP policies on {% data variables.product.prodname_dotcom_the_website %}. Through these policies, you can allow or block MCP server usage entirely, or restrict access to a list of servers that you define in an MCP registry.
+
+## MCP registries
+
+An MCP registry is a directory of MCP servers that acts like a catalog for IDEs and {% data variables.product.prodname_copilot_short %}. Each registry entry points to a server's manifest, which describes the tools, resources, and prompts that server provides.
+
+After you create your MCP registry, you can make it available to your company, allowing you to:
+* Curate a catalog of MCP servers your developers can discover and use without context switching
+* Restrict access to unapproved servers for increased security and compliance
+* Provide clarity to developers when a server is blocked by policy
+
+## MCP policy settings
+
+The following settings let you control how MCP servers are discovered and accessed in your organization or enterprise:
+
+* **MCP servers in {% data variables.product.prodname_copilot_short %}**: Manage the use of MCP servers for all users with {% data variables.product.prodname_copilot_short %} seats in your organization or enterprise.
+* **MCP Registry URL**: Specify the URL of your MCP registry, allowing your developers to discover and use approved MCP servers in supported surfaces.
+* **Restrict MCP access to registry servers**: Choose whether to allow all MCP servers or restrict access to only those listed in your configured registry.
+
+## Supported surfaces
+
+MCP management features are supported as follows:
+
+| Surface | Registry display | Allowlist enforcement |
+|---|:---:|:---:|
+| {% data variables.copilot.copilot_cli_short %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} |
+| {% data variables.copilot.copilot_coding_agent %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} |
+| Eclipse | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+| JetBrains | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+| {% data variables.product.prodname_vs %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} |
+| {% data variables.product.prodname_vscode_shortname %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+| {% data variables.product.prodname_vscode_shortname %} Insiders | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+| Xcode | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+
+> [!NOTE]
+> For Eclipse, JetBrains, and Xcode, MCP management features are supported in the pre-release versions of {% data variables.product.prodname_copilot_short %}.
+
+## Next steps
+
+To create your own MCP registry, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry).

content/copilot/concepts/prompting/response-customization.md

@@ -26,6 +26,8 @@ category:
 
 {% data variables.product.prodname_copilot %} can provide responses that are tailored to your personal preferences, the way your team works, the tools you use, or the specifics of your project, if you provide it with enough context to do so. Instead of repeatedly adding this contextual detail to your prompts, you can create custom instructions that automatically add this information for you. The additional information is not displayed, but is available to {% data variables.product.prodname_copilot_short %} to allow it to generate higher quality responses.
 
+{% data reusables.copilot.custom-insts-nondeterministic %}
+
 ## Types of custom instructions
 
 There are three main types of custom instructions that you can use to customize {% data variables.product.prodname_copilot_short %} responses on the {% data variables.product.github %} website:
@@ -122,6 +124,8 @@ There are two types of files you can use to provide context and instructions to
 
 While custom instructions help to add codebase-wide context to each AI workflow, prompt files let you add instructions to a specific chat interaction.
 
+{% data reusables.copilot.custom-insts-nondeterministic %}
+
 ## About repository custom instructions
 
 You can use three types of repository custom instructions in {% data variables.product.prodname_vscode_shortname %}:
@@ -179,11 +183,14 @@ The following examples demonstrate how to use prompt files.
   …
   ```
 
+For information on how to enable, create, and use prompt files, see [AUTOTITLE](/copilot/how-tos/configure-custom-instructions/add-repository-instructions?tool=vscode#enabling-and-using-prompt-files).
+
 {% data reusables.copilot.custom-instructions-effective %}
 
 ## Next steps
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
+* [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
 
 {% endvscode %}
 
@@ -199,6 +206,8 @@ The following examples demonstrate how to use prompt files.
 
 {% data variables.product.prodname_copilot %} can provide responses that are tailored to the way your team works, the tools you use, or the specifics of your project, if you provide it with enough context to do so. Instead of repeatedly adding this contextual detail to your prompts, you can create a custom instructions file in your repository that automatically adds this information for you. The additional information is not displayed in the chat input box, but is available to {% data variables.product.prodname_copilot_short %} to allow it to generate higher quality responses.
 
+{% data reusables.copilot.custom-insts-nondeterministic %}
+
 ## About repository custom instructions
 
 In {% data variables.product.prodname_vs %}, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
@@ -246,6 +255,8 @@ There are two types of files you can use to provide context and instructions to
 
 While custom instructions help to add codebase-wide context to each AI workflow, prompt files let you add instructions to a specific chat interaction.
 
+{% data reusables.copilot.custom-insts-nondeterministic %}
+
 ## About repository custom instructions
 
 In JetBrains IDEs, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
@@ -322,6 +333,7 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 ## Next steps
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
+* [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
 
 {% endjetbrains %}
 
@@ -337,6 +349,8 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 
 {% data variables.product.prodname_copilot %} can provide responses that are tailored to the way your team works, the tools you use, or the specifics of your project, if you provide it with enough context to do so. Instead of repeatedly adding this contextual detail to your prompts, you can create a custom instructions file in your repository that automatically adds this information for you. The additional information is not displayed in the chat input box, but is available to {% data variables.product.prodname_copilot_short %} to allow it to generate higher quality responses.
 
+{% data reusables.copilot.custom-insts-nondeterministic %}
+
 ## About repository custom instructions
 
 In Xcode, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
@@ -362,6 +376,7 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 ## Next steps
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
+* [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
 
 {% endxcode %}
 
@@ -382,6 +397,8 @@ There are two types of repository custom instructions you can use to provide con
 * **Workspace custom instructions** which apply to all projects in a workspace, and allow you to specify workspace-wide instructions and preferences, in a single file.
 * **Project custom instructions** which apply to a specific project.
 
+{% data reusables.copilot.custom-insts-nondeterministic %}
+
 ## About repository custom instructions
 
 **Workspace custom instructions** apply to all projects in a workspace, and allow you to specify workspace-wide instructions and preferences. You can use workspace custom instructions to provide context and instructions to {% data variables.product.prodname_copilot_short %} in Eclipse.
@@ -405,6 +422,7 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 ## Next steps
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
+* [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
 
 {% endeclipse %}