Connect GitHub when you need Issues
Optional: feedback and MCP work without GitHub. One project uses one App and can connect up to 20 repositories across that App's permitted installations.
- Add an App
- Connect repositories
- Create an Issue
Connect selected repositories
- As the server owner, open Setup → Manage integrations → GitHub → Add GitHub account.
- Choose Encrypted in Feedbacks, enter the account, then Continue to GitHub with an authorized GitHub login. Approve the private App.
- Install it on Only select repositories. Use a separate private App for another owning GitHub account.
- In the project's GitHub tab, choose Save App. Save an exact
https://github.com/OWNER/REPOURL → Connect project. Use Add another repository for more destinations.
Only human server owners manage/select Apps; maintainers connect repositories. Adding a URL grants no GitHub access.
If the connection check fails, choose Retry GitHub connection to load its status again. When no App is selected, the page asks you to configure one instead of leaving the repository check running.
| Credential choice | Operational requirement |
|---|---|
| Encrypted in Feedbacks | Back up database and private storage together |
| Deployment environment | Keep operator secrets; restart after changes |
Both are accessible to the running server. Use HTTPS, limit owners and never share private keys between independent servers. Storage, import and recovery.
Create deliberately
Use Create GitHub issue on the thread; multiple repositories require a destination. For edited text, choose More actions → GitHub issue options → Review/edit first.
Attachment links require Feedbacks sign-in and current project access. One native Issue request is allowed per thread; uncertain writes pause to avoid duplicates. Recover a pending request.
Status sync is opt-in. First mismatches, changes on both sides and uncertain writes pause for a maintainer decision. Changing App clears connections/sync; historical Issue links keep their original App. Sync rules and limits.
Review and share Issue discussion
Open More actions → GitHub issue options → Issue discussion on a thread with a verified linked Issue. A human project maintainer can load a page of up to 20 GitHub comments or write a separate comment, preview its exact text, confirm the destination and queue it. The existing GitHub App needs Issues: read and write on that repository. Each displayed comment is capped at 12,000 characters; open its GitHub link for the complete original.
Only the reviewed text is sent. Feedbacks replies, screenshots and private notes are not automatically mirrored. Delivery history records the result without including the comment body. Current permissions, the original App and the connected repository are checked again before sending.
If a write may have succeeded, automatic retries stop. Inspect the Issue, then enter the actual comment ID to verify delivery or confirm it is absent and retire that action. A new send requires a separately reviewed action. Moving or deleting feedback waits for active or uncertain writes; a move cancels pending comments and retains history for people who can still maintain the original project.