GitHub Copilot App Adds GitHub Enterprise Server Support

A developer workstation linked to private repository servers

GitHub made GitHub Enterprise Server (GHES) account support generally available in the GitHub Copilot app on November 13, 2026. Version 1.2.0 or later can connect to a GHES account so developers can work with remote repositories, issues, and pull requests hosted on their enterprise instance. GitHub still requires an initial GitHub.com or GHE.com sign-in, and cloud sessions are unavailable for GHES.

Account connection workflow
  1. GitHub.com or GHE.com sign-in
  2. Copilot app account settings
  3. Authorize the GHES account
  4. Open a permitted repository, issue, or pull request

What changed when GHES support reached general availability?

The account integration moved from opt-in preview to general availability. For an application team using a self-hosted repository, the practical change is that the Copilot app can work with supported GHES repository context once the developer adds and authorizes that account. This release concerns the Copilot app. Check the documentation for your particular client before assuming the same setup applies to an editor or command-line client.

How to connect a GitHub Enterprise Server account

  1. Check the Copilot app version and use 1.2.0 or later.
  2. Sign in to a GitHub.com or GHE.com account first.
  3. Open Settings → Accounts → Add account → GitHub Enterprise Server.
  4. Follow the browser prompt to authorize the app for your enterprise instance.
  5. Open a repository you already have permission to access. Verify access to one existing issue and pull request before adopting it for regular work.

GitHub’s GHES guide describes using a cloud account with a Copilot license to make requests and points to separate setup for custom model providers. Treat repository access and model configuration as separate checks during rollout.

A practical ASP.NET Core pilot

Use a small repository with a pending validation fix. Open the issue, inspect the pull request and compare the proposed behavior with the existing endpoint tests. Ask for test cases around malformed input and missing fields, then run the relevant tests locally. Keep the repository’s usual pull request review and approval rules in place. If the app cannot find the repository, check the selected account, access in the GHES web interface, and whether the workstation can reach the instance from its current network.

Can GHES repositories use Copilot cloud sessions?

GitHub says cloud sessions are unavailable for GHES. If your workflow depends on them, verify that dependency before moving the workflow into the Copilot app.

Official references

Comments