Codiatech Blog

GitHub Copilot and Enterprise Server: Planning Your First Pilot

GitHub Enterprise Server support is now generally available in the GitHub Copilot app. Here is how to test repository access, model selection and pull request permissions in a controlled pilot.

A small enclosure and three orange cables representing private repository connections

What changed on November 13?

In its November 13, 2026 release note, GitHub made GitHub Enterprise Server (GHES) support generally available in the GitHub Copilot app, starting with version 1.2.0. The feature previously required opting into a preview. Teams can connect a GHES account to work with remote repositories, issues and pull requests in the app. GitHub says cloud sessions are unavailable for GHES.

Validate repository access and model access separately

GitHub’s setup documentation starts with a GitHub.com or GHE.com sign-in, followed by adding the GHES account in the app settings. For model requests, it points to a cloud account with a Copilot license or a separately configured model provider. Give repository access, identity and model data flow separate acceptance criteria. Compare the chosen provider, data allowed in prompts and required network destinations with your organization’s policies.

Start with a low-risk repository

Set up a test repository with synthetic code, a sample issue and a draft pull request. Confirm that an authorized account can open each item. Then use an account with no access to a second repository and verify that access is denied. Write down the expected results for both checks before testing. If a check fails, investigate account setup, network access and repository permissions separately.

Put proposed changes through the existing review process

Two people reviewing a printed workflow for a code change

Use a sample change to verify that a reviewer can inspect the diff, required CI checks run and protected branches reject direct pushes. These are suggested acceptance tests for the pilot. Also check when access ends after disconnecting an account or revoking its repository permissions. Base the decision to expand the pilot on those results.

When does a pilot make sense?

Start with teams already using GHES that want repository, issue and pull request workflows in the desktop app. Teams that specifically need GHES cloud sessions should account for the stated product limit. Verify the app version, model provider and internal policies in the pilot environment. Codiatech addresses these questions in its AI-powered systems and system integration work by mapping them to existing identity, data and operational controls.

Primary source: github.blog