Before you start
- Owner or admin access to the organization in the app.
- Permission to install a GitHub App or authorize an OAuth app on the target repositories.
Step-by-step
- 1
Open the integration
In the dashboard go to Integrations → GitHub and click Connect.
- 2
Authorize with GitHub (recommended)
Choose "Continue with GitHub". You will be redirected to GitHub to approve access. Prefer a GitHub App so you can grant access to specific repositories with fine-grained Issues permissions.
- 3
Token fallback (only if needed)
If you cannot use OAuth, create a fine-grained Personal Access Token limited to the target repositories with Issues: Read and write, and paste it under "manual setup".
- 4
Pick the repository
Select the owner and repository that feedback-driven issues should be created in.
Security best practices
- Prefer a GitHub App over a classic OAuth app — it grants per-repository, fine-grained permissions and short-lived installation tokens.
- Never use a classic PAT with full "repo" scope across all repositories when a fine-grained token will do.
- If you enable inbound events, verify the X-Hub-Signature-256 HMAC on every webhook.
- Credentials are encrypted at rest with AES-256-GCM — they are never stored in plain text.
- Only organization owners and admins can create or modify a connection.
- Prefer OAuth where available: it issues short-lived, scoped, revocable tokens instead of long-lived secrets.
- When you must use a token, create a fine-grained, least-privilege token and rotate it periodically.