GitHub Issues Integration
Auto-create GitHub issues from TigerOps incidents with labels, assignees, trace context, and deployment correlation. Track production incidents directly in your engineering workflow.
How It Works
Create a GitHub Personal Access Token
In GitHub, generate a fine-grained personal access token (or classic token) with repo scope on the target repositories. Grant read/write access to Issues.
Connect GitHub in TigerOps
Enter your GitHub token and target repository (owner/repo format) in the TigerOps GitHub integration panel. TigerOps verifies access by listing existing repository labels.
Configure Label and Assignee Mapping
Map TigerOps severity levels and service tags to GitHub labels. Configure default assignees per service or rely on CODEOWNERS-based auto-assignment.
Incidents Become GitHub Issues Automatically
When a TigerOps incident fires, a GitHub issue is created with title, body, labels, assignees, and trace context. Issue status syncs with incident resolution.
What You Get Out of the Box
Automatic Issue Creation
TigerOps creates a GitHub issue the moment a qualifying incident fires — no manual copy-paste from monitoring dashboards to issue trackers.
Trace and Metric Context in Issue Body
The GitHub issue body includes the AI incident summary, impacted metric snapshot, relevant trace IDs with deep links, and a direct link to the TigerOps timeline.
Smart Label Mapping
TigerOps severity, service name, and environment tags map to GitHub issue labels — so issues for production critical incidents land with the right triage labels immediately.
Deployment Correlation
If TigerOps correlates the incident to a recent deployment, the GitHub issue references the triggering commit SHA and links to the pull request that introduced the regression.
Issue Closure on Resolution
When TigerOps resolves an incident (manually or automatically), the corresponding GitHub issue is closed with a resolution comment including duration and root cause.
Multi-Repo Routing
Route incidents from different services to different GitHub repositories. API service incidents go to the api-service repo, frontend incidents go to the web repo.
GitHub Issue Creation Config
Map TigerOps services to GitHub repositories and configure label and assignee rules.
# TigerOps — GitHub Issues Integration Config
integrations:
github_issues:
token: "${GITHUB_TOKEN}"
default_repo: "yourorg/platform"
min_severity: warning
auto_close: true
dedup_by_incident_id: true
label_mappings:
critical: ["incident", "priority:critical", "production"]
warning: ["incident", "priority:high"]
info: ["incident", "priority:low"]
service_mappings:
- tigerops_service: "api-gateway"
repo: "yourorg/api-service"
labels: ["team:platform"]
assignees: ["platform-lead"]
- tigerops_service: "payments-service"
repo: "yourorg/payments"
labels: ["team:payments"]
assignees: ["payments-oncall"]
issue_template:
title: "[{{severity}}] {{incident_title}}"
body: |
## Incident Summary
{{ai_summary}}
## Affected Service
**Service:** {{service_name}}
**Environment:** {{environment}}
**Severity:** {{severity}}
## Metric Details
- Metric: {{metric_name}}
- Value: {{metric_value}}
- Trace: [View Trace]({{trace_url}})
## Investigation
[Open in TigerOps]({{tigerops_url}})Common Questions
Can TigerOps create issues in GitHub Enterprise Server?
Yes. GitHub Enterprise Server is supported by configuring a custom GitHub API base URL in the integration settings. Use your internal GitHub Enterprise URL (e.g., https://github.yourcompany.com/api/v3) instead of the public GitHub API.
Will TigerOps create duplicate GitHub issues for the same recurring incident?
TigerOps checks for an open GitHub issue with a matching TigerOps incident ID label before creating a new one. If a matching open issue exists, TigerOps adds a comment with the new occurrence data instead of creating a duplicate.
Can I prevent TigerOps from creating GitHub issues for every alert?
Yes. You can configure a minimum severity threshold — for example, only create GitHub issues for critical incidents. You can also restrict issue creation to specific services or environment tags using filter rules in the integration settings.
How does TigerOps handle assignees when there is no CODEOWNERS file?
Without CODEOWNERS, you can configure explicit default assignees per service or per severity level in the TigerOps GitHub integration settings. You can also leave assignees blank and rely on your team's GitHub issue triage process.
Can I link a TigerOps incident to an existing GitHub issue instead of creating a new one?
Yes. From the TigerOps incident panel, you can manually link an existing GitHub issue URL. TigerOps will then post updates and resolution comments to that issue rather than creating a new one.
Turn Incidents into GitHub Issues Automatically
No credit card required. Connect GitHub in minutes. Issues created with full context immediately.