Currently, the Harness GitHub connector primarily supports integration with the public github.com. This limitation prevents organizations that use GitHub Enterprise Server (on-premise) or GitHub Enterprise Cloud with EU data residency (*.ghe.com) from natively connecting their repositories to the Harness platform.

GitHub now offers data residency options, including for the EU, allowing enterprises to store their code and repository data within specific regions to meet compliance and data sovereignty requirements. Harness documentation shows that connections to GitHub Enterprise Server are possible for some modules like SEI (Software Engineering Insights). However, broader and more direct connector support across the Harness platform is needed.

Feature Request: We request that the Harness GitHub connector be enhanced to officially support connections to:

GitHub Enterprise Server: Allow users to provide the URL of their self-hosted GitHub Enterprise instance for a direct integration.

GitHub Enterprise Cloud with EU Data Residency: Support the *.ghe.com domain structure used for GitHub Enterprise Cloud instances with data residency, enabling a seamless connection for organizations with these specific compliance needs.

In addition to the core request for GitHub Enterprise Server and EU data residency support, it is critical that Harness also includes support for OIDC-based authentication for the GitHub connector.

As we are moving to standardized, secure, and passwordless authentication methods. OIDC will be an important feature we are looking forward.