GitHub
Connect GitHub to Koalr for deploy risk, DORA metrics, CODEOWNERS, and PR analytics.
GitHub Integration
The GitHub integration is the foundation of Koalr. Most features — deploy risk, DORA metrics, CODEOWNERS, PR analytics — require GitHub to be connected.
Connecting GitHub
- Go to Settings → Integrations
- Click Connect next to GitHub
- You'll be redirected to GitHub to authorize the Koalr GitHub App
- Select All repositories or specific repositories
- Click Install & Authorize
Koalr requests the following OAuth scopes:
read:org— list your GitHub organization and teamsrepo— read repository contents, PRs, and deploymentsread:user— resolve contributor identities
What Koalr syncs from GitHub
| Data | Sync method | Frequency |
|---|---|---|
| Pull requests (merged) | Webhook + REST backfill | Real-time |
| Deployments | Webhook | Real-time |
| CODEOWNERS files | REST (all repos) | Webhook + daily |
| GitHub Teams | REST | On-demand (import) |
| Check runs / CI status | Webhook | Real-time |
| Repository metadata | REST backfill | On connect |
GitHub Deployments API
Koalr reads deployments from the GitHub Deployments API. If your CI/CD pipeline doesn't create GitHub Deployments, you can also send deployments via:
- Vercel webhook (auto-creates deployment records)
- Railway webhook
- Netlify webhook
- Render webhook
- Fly.io webhook
- AWS CodeDeploy → SNS
CODEOWNERS sync
Koalr parses CODEOWNERS files from 3 locations in each repository:
.github/CODEOWNERSCODEOWNERS(root)docs/CODEOWNERS
Changes to CODEOWNERS files trigger an immediate re-sync via webhook. A daily drift detection cron (3 AM UTC) checks for any divergence and sends Slack alerts if configured.
Troubleshooting
PRs not appearing: Check that the webhook is active in your GitHub App settings. Go to Settings → Developer Settings → GitHub Apps → Koalr → Advanced → Recent Deliveries.
CODEOWNERS not syncing: Ensure the file is in one of the 3 supported locations. Check that the GitHub App has contents: read permission on the repository.
Deployment events missing: Confirm your CI/CD pipeline creates GitHub Deployment records. Many pipelines use gh deployment create or the Deployments API directly.