Frequently asked questions
About DiscoHub, the two-way Discord and GitHub bot.
How is DiscoHub different from GitHub's built-in Discord webhook?
GitHub's Discord webhook (and most GitHub notification bots) is one-way: it posts a message into a channel when something happens on GitHub, and that's the end of it. Nobody can reply, and nothing you do in Discord reaches GitHub. DiscoHub is a two-way sync. A Discord forum post becomes a GitHub issue and an issue becomes a forum post; replies, labels, open/close state, locks, and attachments are mirrored in both directions, so the forum and the issue tracker are two views of the same conversation.
Is the sync really two-way?
Yes. Discord to GitHub: a new post creates an issue, thread messages become comments, and forum tags drive labels, close/reopen, and lock/unlock through the tag actions you configure. GitHub to Discord: a new issue creates a forum post, comments (including edits and deletions) become messages, and label, state, and lock changes update the thread and its tags.
Which Discord channels does it work with?
Forum channels. DiscoHub maps a forum thread to an issue, so it needs threads with a title, a starter post, and tags. Regular text channels aren't supported.
Can one forum channel host several repositories?
Yes. Each linked repo gets its own forum tag, and a post's tag decides which repository its issue is filed in. A post with no repo tag isn't synced automatically; run /sync-thread inside it to file an issue on demand.
Does it work with private repositories?
Yes. Issues, comments, state, and labels sync exactly as for public repos. The one difference is image attachments coming from GitHub: GitHub only serves attachments on private repos to a logged-in browser session, not to an app, so those arrive in Discord as a link rather than an inline image. Attachments posted in Discord still appear inline on GitHub.
Do my Discord members need GitHub accounts?
No. Members post and reply in Discord as usual. DiscoHub writes to GitHub as its own GitHub App and attributes each mirrored message to its Discord author, with a link back to the original, so maintainers see who said what without anyone needing a GitHub account.
What permissions does the bot need?
On Discord: view channels, send messages (including in threads), create and manage threads, manage messages, embed links, attach files, and read message history. It does not ask for Administrator. On GitHub: it installs as a GitHub App scoped to the repositories you choose, with the issue permissions it needs to create and update issues and comments.
What does the Free tier include?
One server, one linked repository, up to three tag actions per forum channel, and no history backfill. New activity syncs from the moment you link. Paid tiers add more linked repos, more tag actions, and backfill of existing issues; they arrive after the beta.
Can I bring existing issues or threads into sync?
On paid tiers, yes: /sync (or the Backfill step in the dashboard wizard) imports existing open issues as forum posts, or existing threads as issues, up to the tier's cap. On Free, sync starts from the link forward.
What happens to my links if I downgrade or cancel?
Links beyond your new tier's allowance are paused rather than deleted (the oldest links stay active). A paused link stops syncing in both directions; nothing already mirrored is removed, and the link resumes as soon as you're back within allowance.
What data does DiscoHub store?
The mappings that make sync work: which thread matches which issue, which message matches which comment, your tag actions, and the GitHub App installation for each server. Attachments posted in Discord are stored so GitHub can display them. DiscoHub runs no analytics or ad tracking. The full details are in the privacy policy.
Something else?
Read the setup guide, the privacy policy, the terms of service, or ask on the support Discord.