Skip to content
Documentation

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.

  1. 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.

  2. 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
  3. 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.

CommandAccessWhat it does
ManagerGuided setup: link GitHub, add a repository, and turn on trackers from buttons and menus.
ManagerLink a GitHub account or organization through Install GitHub App or Already installed, then press Link on the page GitHub sends you to. Options: code.
ManagerUnlink one account, or every account. Trackers pause until one is linked again. Options: account.

Repositories

Register a repository once and every command offers it from a picker.

CommandAccessWhat it does
ManagerRegister a repository (owner/repo, a GitHub URL, or a search of the linked ones). branch defaults to the repository's default branch. A public repository no linked account covers is followed read-only, from the 15-minute check. Options: repo, branch, friendly_name.
ManagerRegistered repositories and plan usage.
ManagerUnregister a repository and remove its trackers, project entries, digests, and reminders. Options: repo.
ManagerChange the display name or branch, or repoint trackers after a GitHub rename. Options: repo, new_repo, new_branch, new_friendly_name.
Manager(Premium) A repository's own color and layout, or clear them. Options: repo, color, layout, clear.
ManagerPick which repositories keep running if the plan stops covering them all.

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.

CommandAccessWhat it does
ManagerPost every new commit on each push. Options: repo, channel, branch (Premium), ignore_bots (Premium), ping_role (Premium), clear_ping.
ManagerPost pull request activity, and review decisions with track_reviews. Options: repo, channel, track_reviews, thread_mode (Premium), branch (Premium), ignore_bots (Premium), ping_role (Premium), clear_ping.
ManagerKeep a live issue board, edited in place. Options: repo, channel, resolved_embed, label (Premium), clear_label.
ManagerPost GitHub Actions runs as they start and finish. Options: repo, channel, detailed_embed, branch (Premium), ignore_bots (Premium), failures_only (Premium), ping_role (Premium), clear_ping.
ManagerPost published releases. Options: repo, channel, ping_role (Premium), clear_ping.
ManagerPost new stars, and optionally forks. Options: repo, channel, track_forks.
ManagerPost new comments on issues and pull requests. Options: repo, channel, ignore_bots (Premium).
ManagerPost new discussions, replies, and answers. Options: repo, channel.
Manager(Premium) Post deployments as they succeed or fail. Options: repo, channel, failures_only, ping_role, clear_ping.
Manager(Premium) Post new Dependabot, code scanning, and secret scanning alerts. Keep the channel private. Options: repo, channel, ping_role, clear_ping.
Manager(Premium) Turn on trackers for many repositories at once, in one channel. Options: channel, scope.
Manager(Premium) Track new repositories on your linked accounts on their own. Options: channel, clear.
ManagerEvery tracker with its settings. Pause, mute, move, remove, or tidy one. Options: repo.

Filters, digests, reminders & insights

Premium. Narrow what a tracker posts, and send summaries and reminders on a schedule.

CommandAccessWhat it does
Manager(Premium) Narrow what one tracker posts. Options: tracker, paths, authors, labels, workflows, contains, excludes.
Manager(Premium) See what a tracker is narrowed to. Options: tracker.
Manager(Premium) Post everything again. Options: tracker.
Manager(Premium) A daily or weekly summary of a repository. Options: repo, channel, frequency, hour, weekday, replaces_live.
Manager(Premium) See digests, with a button to remove each.
Manager(Premium) Remove one digest. Options: digest.
Manager(Premium) Remind a channel about stale pull requests and the review queue. Options: repo, channel, frequency, hour, weekday, stale_days, ping_role.
Manager(Premium) What is waiting for review right now, shown privately. Options: repo.
Manager(Premium) See reminders, with a button to remove each.
Manager(Premium) Remove one reminder. Options: reminder.
Manager(Premium) How often each workflow passes, how long it takes, and whether it is flaky. Options: repo.

People & contributors

Connect GitHub accounts to members, and recognize the people who do the work.

CommandAccessWhat it does
Manager(Premium) Say which member a GitHub account belongs to, for members who don't sign in. Options: github, user.
ManagerRemove a mapping. Options: github.
ManagerSee who is mapped, with a button to unmap each.
All(Premium) Connect your GitHub account with a sign-in button, and turn your own DMs on or off.
Manager(Premium) The top 10 contributors for the week, the last 30 days, or all time. Options: period, metric, repo.
Manager(Premium) One person's numbers, by GitHub username or by a member with a mapped account, or your own. Options: github, user.
Manager(Premium) Post the week's top contributors once a week, without pinging anyone. Options: channel, weekday, hour, repo, clear.
Manager(Premium) Give a role to members who reach a number, such as 100 commits. ForgeFeed's role needs Manage Roles, granted by hand, and so does whoever adds one. Roles that can moderate or manage the server are refused. Options: role, metric, threshold.
Manager(Premium) Stop giving out a contributor role. Options: role.
Manager(Premium) See the contributor roles, with a button to stop giving each.

Project boards

A status board you update by hand, for public roadmaps. Premium adds milestone entries and a board's own statuses.

CommandAccessWhat it does
ManagerPost a project board. Options: channel, title, bar_style.
ManagerAdd a project to a board, or update one. Options: board, repo, status, percent, summary, website.
Manager(Premium) Add a project that follows a GitHub milestone. Options: board, repo, milestone, summary.
Manager(Premium) Give a board its own statuses, 2 to 10 of them, or clear them. Options: board, set, clear.
ManagerUpdate one project's status or percent. Options: project, status, percent.
ManagerSet every project on a board at once. Options: board, status, percent.
ManagerRemove one project from a board. Options: project.
ManagerDelete a project board and its message. Options: board.

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.

CommandAccessWhat it does
ManagerPost a live card for an issue or pull request in this channel, edited as its state, labels, assignees, milestone, and comments change. Up to 25 per server. Options: number, repo.
RoleOpen a GitHub issue from Discord through a form. Options: repo, label.
RoleFrom a message's right-click menu, under Apps. It asks which repository, then opens the form with the message's text filled in.
Role(Premium) From the right-click menu of a message in a pull request's thread, under Apps. It opens a form with the message's text to edit, then posts it as a comment on the pull request, signed with your Discord name. For managers and the role set with /settings actions-role.
ManagerSee which roles can submit issues, or allow or revoke one. Options: role, allow.
ManagerWhere receipts, resolved digests, and reopened notices post. Options: receipts, resolved, reopened, clear.
ManagerA repository's labels and the emoji shown for each. Options: repo.
ManagerChoose the emoji shown beside a label. Options: label, emoji, repo.
ManagerRestore the built-in emoji for one label, or for all of them. Options: label.

Settings, checks & help

Server-wide settings, a health check, the plan, and help.

CommandAccessWhat it does
ManagerEvery setting for this server, with a button to turn setup reminders on or off.
ManagerThe time zone digests, reminders, weekly leaderboards, and quiet hours count their hours in. Posts show their time in each reader's own time zone. Options: zone, clear.
ManagerHours, in the server's time zone, when posts go out without a notification, the way Discord's own @silent works. Role pings and mentions included, and nothing is held back. Options: start, end, clear.
ManagerTurn setup reminders on or off. Options: enabled.
ManagerAlert a channel and up to five roles when the GitHub quota runs low. Options: channel, threshold, role_1 to role_5, clear.
ManagerWhere notices about the bot go, instead of a DM to the owner. Options: channel, clear.
ManagerA role that can run ForgeFeed without Manage Server. Manage Server only. Options: role, clear.
Manager(Premium) A role that can use the buttons on posts. Manage Server only. Options: role, clear.
ManagerCheck why something isn't posting, and what to do about it. Options: repo.
ManagerThe plan, the repository limit, tracker counts, and upgrade buttons.
AllWhat you can use, with links to the documentation and support.

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.

CommandOptionWhat it does
/track commitsbranchPremiumFollow a branch other than the registered one. Run it once per branch to follow several.
/track commitsignore_botsPremiumSkip commits by Dependabot, Renovate, and other bot accounts.
/track commitsping_rolePremiumPing a role on each push.
/track prstrack_reviewsAlso post review decisions, Approved and Changes Requested only. Off by default.
/track prsthread_modePremiumOne live card per pull request instead of a post for each change. Reviews, CI results, comments, and new commits collect in a thread under it.
/track prsbranchPremiumFollow a branch other than the registered one.
/track prsignore_botsPremiumSkip bot pull requests and bot reviews.
/track prsping_rolePremiumPing a role on each post.
/track issuesresolved_embedPost the resolved digest, which credits whoever closed each issue. On by default for a new board.
/track issueslabelPremiumA board that shows only one label, such as a bug board in a support channel.
/track workflowsdetailed_embedAdd the triggering event, the commit, and up to 8 jobs with their results and durations.
/track workflowsfailures_onlyPremiumPost only runs that failed, timed out, or failed to start.
/track workflowsbranchPremiumFollow a branch other than the registered one.
/track workflowsignore_botsPremiumSkip bot activity.
/track workflowsping_rolePremiumPing a role only when a run fails. The failure posts as a new message, so the ping notifies.
/track releasesping_rolePremiumPing a role on each release.
/track starstrack_forksAlso post forks, with a link to the new fork. Off by default.
/track commentsignore_botsPremiumSkip comments by bots.
/track deploymentsfailures_onlyPremiumPost only failed deployments.
/track deploymentsping_rolePremiumPing a role on each deployment that is posted.
/track securityping_rolePremiumPing a role on each alert that is posted.
/filters settrackerPremiumThe tracker to narrow, shown by its repository and kind.
/filters setpathsPremiumFiles changed, for commits. * is anything within a folder, ** is anything at all, and ? is one character.
/filters setauthorsPremiumOnly these GitHub accounts.
/filters setlabelsPremiumPull requests with one of these labels.
/filters setworkflowsPremiumOnly these workflow names.
/filters setcontainsPremiumWords the message, title, or comment must include one of.
/filters setexcludesPremiumWords the message, title, or comment must not include.
/digest setreplaces_livePremiumStop the repository's trackers posting live until the digest is removed. Issue boards, deployments, and security alerts still post.
/reminders setstale_daysPremiumDays without activity before a pull request counts as stale. 3 by default.
/reminders setping_rolePremiumPing a role with each reminder.
/repo brandcolorPremiumA hex color, such as #5865F2.
/repo brandlayoutPremiumcompact, standard, or detailed.

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.

PermissionWhy
View ChannelSee the channels it posts in.
Send MessagesPost updates.
Embed LinksUpdates are embeds.
Read Message HistoryEdit issue and project boards in place.
Mention EveryonePing roles that are not publicly mentionable, for ping_role and rate alerts.
View Audit LogSend the welcome DM to whoever invited the bot, rather than the server owner.
Create Public ThreadsOpen a thread under a pull request's card (thread_mode). Without it, that content posts in the channel.
Send Messages in ThreadsPost 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.

OldNow
/linkgithub/github link
/synclink/github link, then Already installed
/confirmlink/github link, then Enter code, or /github link code:
/unlinkgithub/github unlink
/trackrepo/repo add (its repo_url option is now repo, and branch is optional)
/listrepos/repo list
/untrackrepo/repo remove
/renamerepo/repo edit
/postcommits/track commits
/trackprs/track prs
/trackissues/track issues
/postworkflows/track workflows
/trackreleases/track releases
/trackstars/track stars
/trackingstatus/trackers
/movetracker/trackers, then pick a new channel
/removecommits, /removeprs, /removeissues, /removeworkflows, /removereleases, /removestars/trackers, then Remove
/tidyissues/trackers, pick the issue board, then Tidy board
/createprojecttrack/project create
/setprojecttrack/project add
/setprogress/project progress
/setallprogress/project progress-all
/removeprojectentry/project remove-entry
/removeprojecttrack/project delete
/allow_role_submit_issue/submissions roles
/set_issue_receipt_channel, /set_issue_resolved_channel, /set_issue_reopened_channel/submissions channels with receipts, resolved or reopened
/statuses/labels list
/setstatusemoji/labels emoji
/resetstatusemoji/labels reset
/issuelegendGone: every issue board has its legend
/set_rate_alerts/settings rate-alerts
/settings nudges:/settings reminders
/repo rename/repo edit
board_id on /projectboard
tracker and status on /submitissuerepo and label

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.