Check if you have a GitHub Enterprise Server
The first thing to do is to verify if you have a GitHub Enterprise Server instance, described here on the GitHub documentation, as this document only applies to an GitHub Enterprise Server, and not a repo on hosted on github.com.
Initial application setup
If a member of your team has already set up a GitHub Enterprise Server connection, you can skip to the Gearset setup section of this article.
Depending on your corporate firewall settings, you may need to allowlist logins from Gearset’s static IPs. Next, you will need to create a new OAuth application for Gearset to be able to access your GitHub Enterprise Server instance, by following these steps:
Log in to GitHub Enterprise Server
Go to the
Applicationspage in your organization’s settings. You may also need to navigate toDeveloper settings:
Under
OAuth Apps, clickRegister new applicationEnter the following:
-Gearsetas theApplication name,-
https://app.gearset.comas theHomepage URLand
-https://app.gearset.com/authorization/github-enterprise/callbackas theAuthorization callback URL.
Then clickRegister application
Take note of the Client ID and the Client Secret.
Gearset setup
Now that you have your application Client ID and Client Secret, you can link Gearset with your GitHub Enterprise Server instance.
Navigate to the Source control and services page
Click
+ Connect to GitHub Enterprise ServerFill in the
URLof your GitHub Enterprise Server instance (don’t forget HTTPS), theClient IDandClient Secret(from the earlier step)Press
Connect. You will then go through the normal authentication flow from within GitHub Enterprise.
Once complete, you will be redirected back to Gearset and you should now be able to use GitHub Enterprise Server repositories as your source or target.
Anyone else in your team who wants to connect to GitHub Enterprise Server will need to follow the Gearset setup steps.