GitHub
GitHub is a delivery target for Shingo findings. When Shingo detects a revenue-critical issue, it auto-creates a GitHub issue with the full execution package: root cause, revenue impact, affected code, and suggested fix.
What Shingo does
Creates issues
Auto-drafts GitHub issues with finding details, revenue impact, and fix spec
Adds labels
Priority labels based on dollar impact (critical, high, medium)
Links code
References specific files and line numbers in the issue body
Reads deploys
Correlates deploy history with behavioral changes for causal analysis
Setup
Create a fine-grained personal access token
In GitHub, go to Settings → Developer Settings → Personal access tokens → Fine-grained tokens → Generate new token.
Set repository access
Select the repositories where Shingo should create issues. Grant permissions: Issues (read/write) and Pull Requests (read/write).
Copy the token
The token will look like ghp_... — copy it immediately.
Paste in Shingo
In the Shingo onboarding flow (Step 2: Actions), paste the token in the GitHub connector field.
Key format
# GitHub fine-grained personal access token
ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Example issue
When Shingo finds a revenue-critical issue, the auto-created GitHub issue looks like this:
[Shingo] Mobile checkout validation broken — $1.8M/yr impact
Priority: Critical
Confidence: 94%
Root cause: JS lib v2.4.0 broke mobile form validation in checkout.tsx:142
Impact: $1.8M/yr across 12,847 sessions
Fix: Revert to v2.3.1 or patch validation logic