If you haven't already, you'll need to link your Code Climate user to your GitHub user.
If you've enabled third-party application restrictions on your GitHub organization, you will also need to whitelist Code Climate within GitHub. Until you do so, Code Climate will not have access to your GitHub organization's private repositories. As a result, you won't be able to import private repositories, and GitHub-hosted open source repositories may not display a Settings link to you in our UI.
Please see our step-by-step instructions below to get Code Climate approved as third-party application in GitHub.
- Ensure you are logged into GitHub as a user that is currently linked to your Code Climate user.
- Browse to your GitHub user's -- not your GitHub organization's -- Settings menu. Here is the URL: https://github.com/settings/profile
- Select the Applications tab on the left.
- Select the Authorized OAuth apps tab at the top.
- Click Code Climate.
- Towards the bottom of the page, under Organization access, click Grant access for your GitHub organization.
If you instead see a button named Request access then your GitHub user doesn't currently have the rights to approve third-party applications.
After completing these steps, Code Climate will have access to your repositories. If you see a Sync Now button in Code Climate, click it to re-sync your Code Climate user data with your GitHub user data.
Private forks of organization-owned repositories are subject to the access restrictions of the organization from which the repo was forked. This requires the parent organization (from which the repo was forked) to create a Code Climate org and import the (parent) repo to Code Climate. During this process, Code Climate will prompt the user to enable Code Climate as a third-party application for the organization.
Updated about a month ago