GitHub Integration
Overview
Connect GitHub to enable the Git AI Agent, which correlates code changes with infrastructure incidents during investigations and chat sessions.
What It Enables
- View recent commits and pull requests
- Correlate deployments with incident timelines
- Identify code or configuration changes that caused issues
- Browse file contents and blame information
Setup
1. Start Integration
- In the OpsWorker portal, go to Integrations
- Find GitHub and click Connect
2. Install the GitHub App
- You'll be redirected to GitHub to install the OpsWorker GitHub App
- Select the GitHub organization or account to install it on
- Choose which repositories to grant access to (all or selected)
- Confirm the installation
OpsWorker stores the resulting installation (its installationId) and connects to GitHub through the GitHub MCP endpoint (https://api.githubcopilot.com/mcp/).
3. Configure for Cluster
- Return to the OpsWorker portal
- Associate the GitHub integration with your cluster(s). The integration is stored per cluster.
Permissions
OpsWorker requests the access the GitHub App needs to correlate changes and to propose fixes:
| Permission | Purpose |
|---|---|
| Read repository contents | View files, commits, branches |
| Read pull requests | View PRs and their changes |
| Read commit history | Correlate changes with incidents |
| Write (branches and pull requests) | Open fix branches and pull requests for human review |
OpsWorker is not read-only. The source code agent can create branches and open pull requests with suggested fixes. Those pull requests are always reviewed and merged by a human; OpsWorker never merges on its own.
Use Cases
- Investigation enrichment: when a pod crashes after a deployment, the Git Agent identifies the relevant commit
- Change correlation in chat: "What PRs were merged in the last 24 hours?"
- Configuration drift: compare running config with repository definitions
Next Steps
- Git AI Agent: full agent capabilities
- PR Creation: code-level fix suggestions