JetherVerse News
Software· 1 min read

GitHub Copilot app adds Enterprise Server support

GitHub has made GitHub Enterprise Server support in the Copilot app generally available after an opt-in preview. The app needs version 1.2.0 or later, and cloud sessions are not offered for GHES.

By JetherVerse News

GitHub has made GitHub Enterprise Server support in the GitHub Copilot app generally available. GitHub announced the change on November 13, 2026. The feature was an opt-in preview before.

With the update, you connect a GitHub Enterprise Server account, known as GHES, to the Copilot app. You then work with remote repositories, issues and pull requests from the app. Setup has two steps. First, sign in with a GitHub.com or GHE.com account. Then open Settings, choose Accounts, select Add account and pick GitHub Enterprise Server.

Two limits apply. The app must be version 1.2.0 or later. Cloud sessions are not available for GHES. The announcement says nothing about plans, pricing or usage limits, so check your own agreement with GitHub before you roll the app out to a team.

GitHub Enterprise Server is the self-managed edition of GitHub, run by a company on its own infrastructure. Teams on GHES used the Copilot app through a preview until now. General availability means the connection leaves preview. Administrators should check three things before rollout. Confirm the app version on each developer machine. Confirm each developer holds a GitHub.com or GHE.com sign-in, since the GHES account is added after the first sign-in. Tell teams cloud sessions are not offered for GHES repositories, so plan around this limit.

Pull requests, issues and remote repositories are the three areas the announcement names, so test each one during your trial. Check the Copilot GHES documentation GitHub links for the sign-in steps, and keep a short record of any error messages your team meets during setup.

Developers in Nigeria who serve enterprise clients on self-hosted GitHub should read the Copilot GHES documentation for the full sign-in steps.

If a client runs GHES, test the connection on one machine first and write down the steps for the rest of the team.

Source: GitHub Changelog

Get the news in your inbox

The tech stories that matter from JetherVerse News, with the source on every one.

Free. Unsubscribe any time.