Repo sync

content/code-security/dependabot/dependabot-version-updates/optimizing-pr-creation-version-updates.md

@@ -58,6 +58,8 @@ updates:
 
 See also [schedule](/code-security/dependabot/working-with-dependabot/dependabot-options-reference#schedule-).
 
+{% ifversion dependabot-option-cooldown %}
+
 ### Setting up a cooldown period for dependency updates
 
 You can use  `cooldown` with a combination of options to control when {% data variables.product.prodname_dependabot %} creates pull requests for **version updates**.
@@ -102,6 +104,8 @@ SemVer is supported for most package managers. Updates to new versions for depen
 
 See also [`cooldown`](/code-security/dependabot/working-with-dependabot/dependabot-options-reference#cooldown-).
 
+{% endif %}
+
 ## Prioritizing meaningful updates
 
 You can use `groups` to consolidate updates for multiple dependencies into a single pull request. This helps you focus your review time on higher risk updates, and minimize the time spent reviewing minor version updates. For example, you can combine updates for minor or patch updates for development dependencies into a single pull request, and have a dedicated group for security or version updates that impact a key area of your codebase.

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

@@ -167,6 +167,8 @@ Supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`.
 * Supports only the value `scope`
 * When defined any prefix is followed by the type of dependencies updated in the commit: `deps` or `deps-dev`.
 
+{% ifversion dependabot-option-cooldown %}
+
 ## `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.
@@ -234,6 +236,8 @@ The table below shows the package managers for which SemVer is supported.
 > * If `semver-major-days`, `semver-minor-days`, or `semver-patch-days` are not defined, the `default-days` settings will take precedence for cooldown-based updates.
 > * The `exclude` list always take precedence over the `include` list. If a dependency is specified in both lists, it is **excluded from cooldown** and will be updated immediately.
 
+{% endif %}
+
 ## `directories` or `directory` {% octicon "versions" aria-label="Version updates" height="24" %} {% octicon "shield-check" aria-label="Security updates" height="24" %}
 
 **Required option**. Use to define the location of the package manifests for each package manager (for example, the _package.json_ or _Gemfile_). Without this information {% data variables.product.prodname_dependabot %} cannot create pull requests for version updates. For examples, see [Defining multiple locations for manifest files](/code-security/dependabot/dependabot-version-updates/controlling-dependencies-updated#defining-multiple-locations-for-manifest-files).

content/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp.md

@@ -44,13 +44,13 @@ MCP servers can be configured manually in a configuration file, or through the {
 
 Only MCP servers listed in the {% data variables.product.github %} MCP Registry can be added through the registry. Other servers can be configured manually. See [Configuring MCP servers manually](#configuring-mcp-servers-manually).
 
-1. Visit the [{% data variables.product.github %} MCP Registry](https://github.com/mcp).
-1. In the search bar, search for the MCP server you want to add, then click the MCP server in the list of matches.
-1. On the MCP server page, read the description for details on installation requirements and other important usage information. This may vary between servers.
-1. Click **Install server**, then select **Install in {% data variables.product.prodname_vscode_shortname %}**.
-1. {% data variables.product.prodname_vscode %} will open, on the server's Marketplace page. Click **Install** to add the MCP server to your {% data variables.product.prodname_vscode %} instance.
-1. If further configuration is required, follow the instructions on the MCP server page in the {% data variables.product.github %} MCP Registry.
-1. To check that the MCP server has been added, in the **agent mode** of {% data variables.copilot.copilot_chat_short %}, click the tools icon. A dropdown list will appear, showing all the MCP servers and associated tools that are currently available in your {% data variables.product.prodname_vscode %} instance.
+1. In {% data variables.product.prodname_vscode %}, open the extensions panel by clicking the extensions icon in the sidebar or pressing <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>X</kbd> (Windows/Linux) / <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>X</kbd> (Mac).
+1. In the extensions search bar, click the filter icon and select **MCP Registry** from the dropdown.
+1. If it is your first time using the MCP Registry, follow the prompts on screen to enable the registry.
+1. In the search bar, type the name of the MCP server you want to add and select it from the search results.
+1. On the MCP server's configuration page, click **Install**.
+1. To check that the MCP server is configured correctly, open the command palette by pressing <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) / <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac).
+1. Type and select **MCP: List Servers**. You should see the MCP server listed as a configured server.
 
 ### Configuring MCP servers manually
 

content/copilot/how-tos/provide-context/use-mcp/set-up-the-github-mcp-server.md

@@ -26,14 +26,15 @@ The {% data variables.product.github %} MCP server is available to all {% data v
 
 The {% data variables.product.github %} MCP server in {% data variables.product.prodname_vscode %} can be configured remotely or locally. The remote {% data variables.product.github %} MCP server is hosted by {% data variables.product.github %} and is the recommended option for most users. The local {% data variables.product.github %} MCP server is hosted on your machine and is recommended for users who want to customize their setup or have specific security requirements.
 
-The steps below describe remote configuration with one-click OAuth authentication. For information on manually configuring the remote or local {% data variables.product.github %} MCP server, see the [{% data variables.product.github %} MCP server documentation](https://github.com/mcp/github/github-mcp-server).
-
-1. Go to the [{% data variables.product.github %} page of the MCP Registry](https://github.com/mcp/github/github-mcp-server).
-1. Click **Install MCP server** and select **Install in {% data variables.product.prodname_vscode %}**.
-1. In {% data variables.product.prodname_vscode %}, on the {% data variables.product.github %} MCP Server configuration page, click **Install**.
-1. In the popup, when prompted to authenticate, click **Allow**.
-1. In your browser, you will be prompted to authorize. To the right of your profile picture, click **Continue**.
-1. Follow the prompts on screen to complete the authorization process.
+The steps below describe remote configuration through the MCP marketplace in {% data variables.product.prodname_vscode %}'s extension panel. The MCP marketplace is powered by the {% data variables.product.github %} MCP Registry. See [MCP Registry](https://github.com/mcp).
+
+For information on manually configuring the remote or local {% data variables.product.github %} MCP server, see the [{% data variables.product.github %} MCP server documentation](https://github.com/mcp/github/github-mcp-server).
+
+1. In {% data variables.product.prodname_vscode %}, open the extensions panel by clicking the extensions icon in the sidebar or pressing <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>X</kbd> (Windows/Linux) / <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>X</kbd> (Mac).
+1. In the extensions search bar, click the filter icon and select **MCP Registry** from the dropdown.
+1. If it is your first time using the MCP Registry, follow the prompts on screen to enable the registry.
+1. In the search bar, type `github` and select the {% data variables.product.github %} MCP server from the search results.
+1. On the {% data variables.product.github %} MCP server configuration page, click **Install**.
 1. To check that the {% data variables.product.github %} MCP server is configured correctly, open the command palette by pressing <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) / <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac).
 1. Type and select **MCP: List Servers**. You should see `github` listed as a configured server.
 

data/features/dependabot-option-cooldown.yml

@@ -0,0 +1,6 @@
+# References:
+# Issue #19055 - Dependabot updates ecosystem support [GA]
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.19'