GitHub Integration
Connect your repositories and automate issue creation from feedback
Overview
DebugGo's GitHub integration enables seamless synchronization between user feedback and your development workflow. Automatically create issues from bug reports, track their status, and keep your team informed.
Permissions
DebugGo requests the minimum permissions necessary to function:
Repository Access
Read and write access to issues and pull requests
- Create and update issues
- Add labels and assignees
- Post comments
Webhook Events
Automatically configured webhooks for:
- Installation events
- Repository changes
- Issue updates
Configuration
1. Connect GitHub Account
During onboarding, you'll be prompted to connect your GitHub account. This creates a GitHub App installation.
2. Select Repositories
Choose which repositories DebugGo can access. You can start with specific repos and add more later.
3. Configure Project Settings
In your DebugGo project settings, select which repository to create issues in:
- Go to Dashboard → Projects → Your Project
- Click on "GitHub Settings" tab
- Select your target repository
- Configure issue labels (optional)
- Save changes
Webhook Events
DebugGo automatically handles these GitHub webhook events:
installation
Triggered when the app is installed or uninstalled
installation_repositories
Triggered when repositories are added or removed
issues
Syncs issue status changes back to DebugGo
Troubleshooting
- Verify the GitHub App is installed for your repository
- Check that a repository is selected in project settings
- Ensure auto-create is enabled for bug reports
The repository list only shows repos where the GitHub App is installed. Add more via GitHub → Installed Apps → Configure.
You can always modify your GitHub integration settings at github.com/settings/installations
Security
DebugGo follows GitHub's security best practices:
JWT Authentication
All API calls use short-lived JWT tokens
Webhook Verification
All webhooks are verified using HMAC signatures
Minimal Permissions
We only request permissions necessary for core functionality