Some users have asked us why some GitHub repositories were missing in Gearset for selection (e.g. on Compare and deploy page) for their source control connection.
Often, this turns out to be the case that during the initial setup Gearset was granted access to the personal repositories for the GitHub account, but not for organization repositories.
Revoke app access in GitHub
Revoking application access in GitHub and re-adding gives you another chance to give access to your organization repositories.
To do it in GitHub web application, click on your profile icon (top right corner), navigate to Settings > Applications > Authorized OAuth Apps > Gearset Deploy and click the Revoke button (see images below).
Steps after you've revoked app access in GitHub
After revoking Gearset's access permission in GitHub, navigate to Source control and services page in Gearset.
Click on + Connect to GitHub to re-authorize the repository permission of your GitHub account, or connect a different GitHub account (if applicable).
Note: You may need to click the bin icon first to remove the existing GitHub connection, and to see this option to re-connect your GitHub again: + Connect to GitHub.
There could be button called "Grant" which you have to click to provide access to your organization.
The green check mark will be shown confirming that the access is granted.
Clicking on Authorize Gearset button will grant the repository access you are requesting.
Check if your GitHub user is missing organization access
If you still encounter the error "Gearset can't find any repositories. Either create one or update your security settings in GitHub to grant access" - it is possible that your GitHub organization requires permissions higher than your GitHub user has to access your repos.
To check this, go to Settings > Applications > Authorized OAuth Apps > click the button Gearset Deploy and check if you see the following message: "Access request pending" (image below).
In this case, you need to contact the GitHub organization owner to approve (they would get a notification about this).
For more information see GitHub’s documentation:
Requesting organization approval for OAuth apps
When your Gearset connects with your source control, make sure you request access to the organization via the Request button.
Check Team security settings in Gearset
Team Owners on the Gearset team should also check our Team security page to confirm there is no restriction added in the "Source control providers" section.
A configured restriction may prevent other members of the Gearset from accessing their GitHub repositories (e.g. repos which user(s) can preview directly on their GitHub account).
Example with no restrictions in place:
For organization repositories - check with repo owner(s) if your GitHub user has required permissions
If you've tried all the above options, but the error is still blocking you from accessing your organization's repositories, we recommend the below steps.
Check with the owner(s) of repository if your GitHub user has below permissions assigned in GitHub:
Permission: "Metadata" repository permissions (read)
In case of errors with status codes: 200 or 404 related to listing repository collaborators.
In case of errors with status codes: 204 or 404 related to checking if a user is repository collaborator.
In case of errors with status codes: 200 or 404 related to getting a repository permission for a user.
Permission: "Administration" repository permissions (write)
In case of errors with status codes: 201, 204, 403 or 422 related to adding a repository collaborator.
In case of errors with status codes: 204, 403 or 422 related to removing a repository collaborator.
Note: You may need to get in touch with our support via in-app chat for further support on the type of error message surfaced by GitHub if this isn't specified in Gearset app.
More information on all the status codes and error messages in GitHub's documentation.