Skip to content

Repo sync #41011

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 27, 2025
+5 −2
Merged

Repo sync #41011

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7c65cc0
Revise GitHub MCP server setup instructions (#58204)
sj Oct 27, 2025
ccc986f
add information on running conifg apply after upgrade a node (#58180)
zheng022 Oct 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions ...rading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,9 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
tail -f /data/user/common/ghe-config.log
```

The configuration runs in the background and you don't need to run `ghe-config-apply` explicitly unless you encounter a problem.
> [!WARNING] If you are upgrading a node in a multi-node cluster, running `ghe-config-apply` on the command line or saving settings in the {% data variables.enterprise.management_console %} may fail and result in an incomplete upgrade if not all the nodes are upgraded to the same version. Please use `ghe-single-config-apply` instead.
1. Optionally, after the upgrade, validate the upgrade by configuring an IP exception list to allow access to a specified list of IP addresses. See [AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list).
1. For single node upgrades, perform any post-upgrade tasks including disabling maintenance mode so users can use {% data variables.location.product_location %}.

Expand Down
4 changes: 2 additions & 2 deletions content/copilot/how-tos/provide-context/use-mcp/set-up-the-github-mcp-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ The steps below describe remote configuration through the MCP marketplace in {%
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?ref_product=copilot&ref_type=engagement&ref_style=text).

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 extensions search bar, click the filter icon and select **MCP Server** from the dropdown.
1. If it is your first time using the MCP Servers Marketplace, follow the prompts on screen to enable the Marketplace.
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).
Expand Down
Loading