Everything you need to get up and running
Run /setup to link GitHub, add a repository and turn on trackers. Manager commands need Manage Server or a manager role you set, and every manager reply is private to you.
Getting started
Three steps. There is nothing to type, unless you link a second server with a code. Every step also has its own command for admins who want options: /github link, /repo add, and the /track commands.
- 01
Add ForgeFeed
Invite the bot to your server. It posts a welcome with a Connect a repo button in the server, and DMs whoever added it a welcome pointing at /setup. It never reads message content.
- 02
Run /setup
One private message walks an admin through four steps: link GitHub with a button on the page GitHub sends you to, pick a repository, pick a channel, and choose what to post. Nothing needs typing.
❯ /setup - 03
Done
ForgeFeed posts a labelled sample from the repository's latest activity straight away, and the issue board appears too. Everything else posts from the next update on, and nothing from the past is replayed. /trackers lists everything afterwards.
❯ /trackers
After joining, ForgeFeed posts a welcome with a Connect a repo button in the server, and DMs whoever invited it a pointer to /setup (or the server owner, if it cannot tell who that was). When setup finishes it posts a sample from the repository's latest activity, labelled as a sample, and the issue board appears straight away. Everything else posts from the next update on. Nothing else from the past is replayed.
Core concepts
Five ideas explain how everything fits together.
Linked account
ForgeFeed reads GitHub as a GitHub App. A server links one or more installations of that app. Each only reaches the repositories its owner granted, and has its own GitHub quota of 5,000 requests an hour, so one busy server cannot slow down another.
Tracked repository
A repository is registered once per server, with /setup or /repo add. After that every command offers it from a picker. Repositories a linked account can access get everything. A public repository no linked account covers can be added with /repo add and is followed read-only: commits, pull requests, releases, workflow runs, stars and the issue board update from the 15-minute check instead of by webhook, and comments, discussions, deployments, security alerts, the buttons on posts and the issue forms don't work for it. It counts toward the plan like any other, and the server still needs a linked account. A private repository needs a linked account that can reach it.
Tracker
One repository, one kind of update and one channel, for example “commits on acme/app to #dev.” A server can have up to 30 trackers on Free and 300 on Premium, in as many channels as you like.
Plan
Each server is Free or Premium. The plan sets how many repositories it can register (1 on Free, 10 or 25 on Premium), how many trackers it can have (30 or 300), how many GitHub accounts it can link (one on Free, personal or organization), and which Premium options it can use. Free has every tracker type except deployments and security alerts.
Delivery
GitHub webhooks deliver updates in real time, typically within a second. A catch-up sweep every 15 minutes posts anything a webhook missed, for example while the bot restarted, up to 5 missed updates per tracker per sweep. It covers commits, pull requests, issue boards, workflow runs, releases and stars. Comments, discussions, deployments and security alerts are webhook only. A server with no linked GitHub account is not checked at all.
Who can run what
Each command in the reference is marked with one of these levels. Every manager reply is private to the person who ran it.
- Manager
- Anyone with Discord's Manage Server permission, or a role a server sets with /settings manager-role. Discord only shows these commands to Manage Server by default, so a manager role also needs allowing under Server Settings > Integrations > ForgeFeed.
- Role
- Members holding a role an admin allows with /submissions roles, for /submitissue and Create GitHub issue. On Premium, Comment on GitHub and the buttons on posts are for the role set with /settings actions-role instead. Managers can always use all of them.
- All
- Anyone in the server, for /help, and /mygithub on Premium.
- Manage Server only
- /settings actions-role and /settings manager-role need Manage Server itself, so a manager role cannot change them.
Command reference
Twenty commands, grouped by what you are doing, plus Create GitHub issue and Comment on GitHub on a message's right-click menu under Apps. Manager, Role and All show who can run each one, as set out above.
71 commands and subcommands
Setup & linking
Guided setup, and the GitHub accounts a server can use. Admin means Manage Server or the role set with /settings manager-role, and a manager role also needs allowing under Server Settings > Integrations > ForgeFeed.
Repositories
Register a repository once and every command offers it from a picker.
Trackers
Running a /track command again for the same repository and channel changes only the options you fill in. A new tracker starts from the latest update and never replays history. repo can be left out when the server tracks just one repository.
Filters, digests, reminders & insights
Premium. Narrow what a tracker posts, and send summaries and reminders on a schedule.
People & contributors
Connect GitHub accounts to members, and recognize the people who do the work.
Project boards
A status board you update by hand, for public roadmaps. Premium adds milestone entries and a board's own statuses.
Issues, comments & labels
Let members with a role you allow file GitHub issues from Discord, keep a live card for one issue, comment on pull requests from their threads, and choose the emoji drawn beside each label. Role means a role an admin allows with /submissions roles, or for Comment on GitHub the role set with /settings actions-role.
Settings, checks & help
Server-wide settings, a health check, the plan, and help.
Every manager reply is private to the person who ran it. /submitissue is limited to the roles you allow with /submissions roles, and Create GitHub issue is for the same people. Comment on GitHub is for managers and the role set with /settings actions-role.
Tracker options
Options are named exactly as they appear in Discord. To change a tracker, run its /track command again for the same repository and channel; options you leave out keep their current setting. Choosing a Premium option on Free changes nothing and replies with the upgrade options.
clear_ping and clear_label switch ping_role and label off again, and are free on every plan. Options marked Premium need Premium, from $4.99 a month for 10 repositories.
What runs on its own
Things ForgeFeed handles without a command, so a tracker keeps working when the repository around it changes.
- Renames and transfers are followed
- A renamed or transferred repository is followed automatically and the server owner is told. /repo edit covers the cases GitHub does not report: a transfer to an account the app isn't installed on, or a server that already tracked the new name.
- Failing trackers pause
- A tracker whose repository was deleted or lost access is paused, and the server is told. Paused trackers are re-checked every 6 hours and resume on their own when access comes back.
- GitHub outages are recognised
- When GitHub is failing for everyone, trackers aren't paused or reported as broken.
- Uninstalling keeps your trackers
- Uninstalling the GitHub App unlinks it from every server it was linked to, and owners are told. Suspending it, or removing a tracked repository from its access, is reported too. Trackers are never deleted by any of these; they resume when access is back.
- Old links must be confirmed
- A link made before the owner check must be confirmed within 14 days, or it is unlinked with its trackers kept. Reconfirm on GitHub, or Keep linked on the page, does it.
- No linked account, nothing checked
- A server that tracks repositories with no account linked gets one DM to its owner pointing at /setup. /trackers and /setup say why nothing is posting.
- Missing permissions are caught
- Channel permissions are checked when a tracker is set up, and the owner is messaged if they are lost later.
- Announcement channels publish
- A tracker posting in an announcement channel publishes each post to the servers that follow it, up to Discord's limit of 10 an hour per channel. Past that, posts stay in the channel unpublished until the hour is up. It needs nothing beyond Send Messages.
- Spam protection
- A channel that gets more than 12 posts in a minute (30 on Premium) pauses for 5 minutes and posts one notice naming the repository. Updates during the pause are skipped, not queued, and when it lifts one post counts what was skipped, by repository and kind. Issue and project boards keep updating. On Premium, releases, failed runs and security alerts still post, up to 60 in one pause.
- Quiet boards cost nothing
- Boards are only edited when what they show actually changed, and a busy repository's issue events are folded into one redraw.
- Plan changes never delete anything
- When a plan's repository limit drops, the repositories picked with /repo keep stay active, then the ones registered first, and the rest pause, keeping their trackers and settings. /repo list marks them.
- Setup reminders
- A server that has never tracked a repository gets at most two reminders, on day 3 and day 10 after joining. Tracking a repository cancels them, and /settings reminders turns them off.
- Removal is reversible for 90 days
- Removing the bot keeps a server's setup for 90 days, so adding it back restores everything. After that it is deleted.
Discord permissions
The invite link uses the bot and applications.commands scopes and asks for permissions=309237861504, the eight permissions below. The bot does not read message content and has no Message Content intent.
| Permission | Why |
|---|---|
| View Channel | See the channels it posts in. |
| Send Messages | Post updates. |
| Embed Links | Updates are embeds. |
| Read Message History | Edit issue and project boards in place. |
| Mention Everyone | Ping roles that are not publicly mentionable, for ping_role and rate alerts. |
| View Audit Log | Send the welcome DM to whoever invited the bot, rather than the server owner. |
| Create Public Threads | Open a thread under a pull request's card (thread_mode). Without it, that content posts in the channel. |
| Send Messages in Threads | Post reviews, CI, and comments in that thread. |
| Manage Roles (granted by hand) | Left out of the invite on purpose. Only /contributors role-add needs it, and a server grants it to ForgeFeed's role itself. |
Without the two thread permissions the integer is 216192, and pull request threads post in the channel instead. Without Mention Everyone as well it is 85120, and role pings then only reach roles set to be mentionable. Without View Audit Log the bot still works and the welcome message goes to the server owner. Contributor roles also need Manage Roles, which the invite leaves out on purpose: give it to ForgeFeed's role, and the command says so when it is missing. The bot sets its server nickname to ForgeFeed when it joins.
What changed
These command names stopped working on 09-27-2026, when 42 commands became 12. The last five rows are the renames of 11-06-2026. Use the name in the right-hand column.
Ready to link your first repo?
Add ForgeFeed, run /setup, and pick which updates go to which channel from a menu.
Need more accounts or repositories? Premium, from $4.99 a month for 10 repositories
Join the Discord servers already running ForgeFeed.