GitHub

Create GitHub issues automatically when incidents are opened, update labels on status change, close issues on resolve, and add timeline comments.

Setup

1. Go to Settings > Integrations > GitHub in the Batida dashboard.
2. Click Connect GitHub to authorize via OAuth. You will be redirected to GitHub's authorization page.
3. Select the repository (or repositories) where incident issues should be created.
4. Grant the repo and issue scopes when prompted.
5. Return to Batida and confirm the connection.

Repository:  your-org/incident-tracking
Scopes:      repo, public_repo, read:org

Organization access

If the repository belongs to a GitHub organization, ensure the Batida GitHub App has been approved by an organization admin. Requests will appear in the organization's installed apps settings.

Auto-create issues

When an incident is opened, Batida creates a GitHub issue with:

Batida field	GitHub issue field
Incident title	Issue title
Description	Issue body (rendered as Markdown)
Severity	Label (severity:critical, severity:high, ...)
Team	Label (team:backend, team:infra, ...)

The issue body includes a link back to the Batida incident page and a summary table with key metadata.

Example issue body

## Batida Incident: API latency spike

| Field | Value |
|-------|-------|
| **ID** | INC-42 |
| **Severity** | critical |
| **Status** | investigating |
| **Assigned** | @jane |
| **Opened at** | 2026-04-20 14:30 UTC |

[View incident in Batida](https://app.batida.io/incidents/42)

Label updates on status change

When an incident status changes, Batida updates the GitHub issue labels:

Batida status	GitHub label added	GitHub label removed
Investigating	status:investigating	All other status:* labels
Identified	status:identified	status:investigating
Monitoring	status:monitoring	status:identified
Resolved	status:resolved	All other status:* labels

The issue is also closed when the incident is resolved.

Timeline comments

Every timeline entry added in Batida is posted as a comment on the GitHub issue, including the author, timestamp, and message content.

Troubleshooting

• "Repository not found": Verify the app has access to the selected repository. Check the installed apps list on GitHub.
• Labels not created: Batida creates labels on the first incident. If label creation fails, check the repository permissions (repo scope is required).
• Issues not closing: Ensure the GitHub token has not expired. Re-authorize from the integration settings page.