Merge pull request #45343 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/concepts/enterprise-fundamentals/enterprise-accounts.md

@@ -60,7 +60,7 @@ Teams can be synced with IdP groups, allowing you to manage any privileges that
 
 Repositories host files such as your company's source code or internal documentation. They are where developers typically do their work, and they contain their own features and administration options that need to live closer to the code, such as {% data variables.product.prodname_actions %} workflows.
 
-Repositories are owned by organizations and are not directly accessible under the enterprise account.{% ifversion custom-properties-enterprise %} However, your enterprise can define custom properties to apply the same governance model to all repositories with shared characteristics. For example, if you do not want anyone to delete repositories that contain production code, this is something you can govern from the enterprise level.{% endif %}
+Repositories are owned by organizations and are not directly accessible under the enterprise account.{% ifversion custom-properties-enterprise %} However, your enterprise can define custom properties to apply the same governance model to all repositories with shared characteristics.{% endif %} {% ifversion repo-policy-rules %} For example, if you do not want anyone to delete repositories that contain production code, this is something you can govern from the enterprise level.{% endif %}
 
 {% ifversion ghec %}
 

content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/managing-custom-properties-for-repositories-in-your-enterprise.md

@@ -13,7 +13,7 @@ category:
 
 Custom properties allow you to decorate your repositories with information such as compliance frameworks, data sensitivity, or project details. Custom properties are private and can only be viewed by people with read permissions to the repository. An enterprise can have up to 100 property definitions. An allowed value list can have up to 200 items.
 
-Defining custom properties at the enterprise level allows you to create consistent values that users can apply to repositories. With custom properties in place, you can apply consistent governance across repositories in your enterprise by creating a ruleset or repository policy targeting repositories with certain properties.
+Defining custom properties at the enterprise level allows you to create consistent values that users can apply to repositories. With custom properties in place, you can apply consistent governance across repositories in your enterprise by creating a ruleset{% ifversion repo-policy-rules %} or repository policy{% endif %} targeting repositories with certain properties.
 
 ## Allowed characters
 

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

@@ -150,8 +150,6 @@ When {% data variables.copilot.copilot_code-review_short %} is enabled for these
 
 ## MCP servers and agent skills for code review
 
-{% data reusables.copilot.code-review.skills-and-mcp-preview-note %}
-
 {% data variables.copilot.copilot_code-review_short %} can use repository-level agent skills and MCP servers when they are relevant to the review.
 
 {% data variables.copilot.copilot_code-review_short %} is more likely to use skills and MCP context when your repository or pull request gives clear signals, including review-focused skill directory names, custom instructions that reference MCP context, and pull request descriptions that include identifiers referencing configured MCP servers such as issue keys or incident IDs.

content/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers.md

@@ -31,8 +31,7 @@ As a repository administrator, you can configure MCP servers for use within your
 This repository-level MCP configuration is shared by {% data variables.copilot.copilot_cloud_agent %} and {% data variables.copilot.copilot_code-review_short %}. For information on disabling use of MCP servers by {% data variables.copilot.copilot_code-review_short %}, see [Disabling MCP tools for {% data variables.copilot.copilot_code-review_short %}](#disabling-mcp-tools-for-code-review).
 
 > [!NOTE]
-> * Support for agent skills and MCP servers with {% data variables.copilot.copilot_code-review_short %} is in {% data variables.release-phases.public_preview %} and subject to change.
-> * Existing repository MCP configurations that were previously managed under {% data variables.copilot.copilot_cloud_agent %} settings were automatically moved to the new shared MCP settings page. No migration action is required.
+> Existing repository MCP configurations that were previously managed under {% data variables.copilot.copilot_cloud_agent %} settings were automatically moved to the new shared MCP settings page. No migration action is required.
 
 The {% data variables.product.github %} MCP server and Playwright MCP server are enabled by default. You can add your own MCP servers alongside these defaults.
 
@@ -385,9 +384,6 @@ For information on using the {% data variables.product.github %} MCP server in o
 
 ## Disabling MCP tools for code review
 
-> [!NOTE]
-> Support for agent skills and MCP servers with {% data variables.copilot.copilot_code-review_short %} is in {% data variables.release-phases.public_preview %} and subject to change.
-
 In repository settings, use of MCP tools by {% data variables.copilot.copilot_code-review_short %} is enabled by default.
 
 Disable this setting if you want the configured MCP servers available only for {% data variables.copilot.copilot_cloud_agent %}, and not for {% data variables.copilot.copilot_code-review_short %}.

content/copilot/how-tos/copilot-on-github/use-copilot-agents/copilot-code-review.md

@@ -72,8 +72,6 @@ By default, you request reviews from {% data variables.product.prodname_copilot_
 
 ## MCP servers and agent skills
 
-{% data reusables.copilot.code-review.skills-and-mcp-preview-note %}
-
 {% data variables.copilot.copilot_code-review_short %} can use agent skills and MCP servers configured in the repository, when they are relevant to the review.
 
 To make these available for {% data variables.copilot.copilot_code-review_short %} on {% data variables.product.github %}, configure:

content/copilot/how-tos/use-copilot-agents/request-a-code-review/use-code-review.md

@@ -84,8 +84,6 @@ To automatically request re-reviews from {% data variables.product.prodname_copi
 
 ## MCP servers and agent skills
 
-{% data reusables.copilot.code-review.skills-and-mcp-preview-note %}
-
 {% data variables.copilot.copilot_code-review_short %} can use agent skills and MCP servers configured in the repository, when they are relevant to the code being reviewed.
 
 To make these available for {% data variables.copilot.copilot_code-review_short %} on {% data variables.product.github %}, configure:

data/features/custom-properties-enterprise.yml

@@ -1,3 +1,4 @@
 # Repository custom properties defined at the enterprise level
 versions:
   ghec: '*'
+  ghes: '>= 3.18'

data/reusables/copilot/code-review/mcp-context-usage.md

@@ -4,4 +4,4 @@
 * Your agent skills or custom instructions explicitly tell {% data variables.copilot.copilot_code-review_short %} to use specific MCP context.
 * Pull request descriptions reference items available through configured MCP servers, such as issue keys or incident IDs.
 
-To verify which MCP context {% data variables.copilot.copilot_code-review_short %} used for a specific review, open the linked review session from the pull request timeline, then check the session logs to see which MCP servers and tools were called.
+To verify which MCP context {% data variables.copilot.copilot_code-review_short %} used for a specific review, check if there are attributions at the bottom of each review comment. These attributions reference the specific agent skill or MCP server that {% data variables.copilot.copilot_code-review_short %} used to generate that comment. You can also open the linked review session from the pull request timeline, then check the session logs to see which MCP servers and tools were called.