Connecting to your source control repository with Gearset allows you to deploy to and from your source of truth. This article shows you how simple it is to connect to your cloud-based repo on https://github.com/.
If your GitHub repository is not on the URL https://github.com/, it's likely you have an on-premise instance, called GitHub Enterprise Server. We have a separate document to guide you through that process:
Once you're logged into Gearset, head to the Source control and services section and click on the Connect to GitHub link.
This will take you to GitHub's OAuth page for authentication.
Once complete, it should look like this (with your authenticated GitHub username being visible):
Common issues with being unable to access the repos
Organization access
Double-check that your organization has given us access to your repo. If not, you may need to request it from your repo owners. Once you are happy to proceed, click on the Authorize Gearset button to continue and input your password. See this article for more information on this.
Third-party application access policy
Also check that your access policy isn't blocking Gearset from viewing the repo. If you see below restriction, then Gearset may be unable to read your organization's repo:
You may want to click on Yes, remove application restriction to allow Gearset app to be able to access your repo.
Authorized apps
Additionally, your GitHub applications settings should show you an authorized app, called Gearset Deploy. You have the ability to revoke the application at any time.
