GitHub Setup
Connect GitHub repositories through the Codity GitHub App. Dashboard sign-in and App installation are separate steps.
Prerequisites
Use a GitHub account with access to the intended repositories. An organization owner or a user permitted by the organization must install or approve the App. Organization policies may require an approval request.
Setup Steps
Step 1: Sign In and Select an Account
Choose GitHub on the Codity Platform sign-in page. Complete authorization and the welcome flow. Select the personal account or organization that owns the repositories.
Step 2: Install the Codity GitHub App
- Open Repositories and choose Add Repositories.
- On GitHub, select the account or organization for the installation.
- Choose All repositories or Only select repositories. With selected access, include every repository you want Codity to process.
- Review the permissions and complete installation or request approval.
- Return to Codity and refresh Repositories if the installation has not appeared yet.
Step 3: Grant Required Permissions
GitHub's installation screen shows the permissions requested by the deployed Codity App. Review features need repository content access and permission to read pull requests and post feedback. Status/check reporting and code-writing features can require additional permissions. Use that installation screen as the exact requested permission set; do not create an unrelated PAT or assume sign-in authorization installs the App.
For the provider's installation and approval rules, see GitHub's App installation guide.
Step 4: Enable Repositories
For GitHub, repository access is selected on the App installation. Use Add Repositories to revisit the installation flow or manage the installed App in GitHub to change selected repositories. There is no GitLab-style token form in this workflow.
Step 5: Verify Setup
Check that a selected repository appears in the active Codity account. Open a test PR on an eligible branch and check for review activity. See Quickstart verification. Review duration varies.
Troubleshooting
Repository missing: confirm the active account, App installation and selected-repository access. An organization approval request must be approved before access is available.
PR gets no review: check repository access, review triggers, branch conditions and the integration's webhook delivery. Contact your deployment administrator if installation events are not reaching Codity.
A code-writing action fails: verify its feature setting and the App's requested write permissions. Read-only review access does not establish permission to push fixes.
Best Practices
Start with a test repository. Add repositories deliberately, and check access again after transferring a repository or changing organization policies.
Managing Installation Access
Add Another Repository
If the installation uses Only select repositories, grant the App access to the additional repository in the installation settings. Return to the intended Codity account and refresh the repository list. App access and account selection must both match the repository's owner.
For example, an installation on your personal account does not connect example-company/payments. Select the company account and use its App installation, with organization approval where required.
Remove Repository Access
Change the installed App's repository selection when it should no longer have access to a repository. Removing access can affect reviews and other provider-backed workflows. If the goal is to keep the integration connected but stop automatic reviews, use review trigger settings instead.
Diagnose a Missing Review
- Confirm the PR repository is selected in the App installation for the intended owner.
- Check that the dashboard is using that personal/organization account.
- Check effective trigger, target-branch scope and opt-out markers.
- Inspect available run status and provider notification errors. Ask your deployment administrator to inspect App webhook delivery if you cannot access that information.
- If an App permission update is pending approval, have the authorized account complete it, then test again.
Do not create a PAT merely because a GitHub repository is absent. This repository-integration flow uses the App installation. CLI credentials are documented separately in CLI Authentication.

