Every GitHub signal, beautifully in Discord
Ten kinds of tracker, each posting to its own channel. Free covers eight of them. Premium adds deployments and security alerts, plus filters, digests and reminders to shape what gets posted.
What every tracker runs on
Real-time by default
GitHub webhooks deliver updates typically within a second. A catch-up sweep every 15 minutes posts what a webhook missed, such as during a restart, up to 5 updates per tracker per sweep.
Multi-account & orgs
Link a personal account and organizations to the same server, each reaching only the repositories its owner granted. (Premium)
Secure by design
GitHub App authentication and verified installation linking. ForgeFeed never sees your GitHub password or personal access tokens.
Resilient & self-healing
Renamed and transferred repositories are followed automatically. A tracker that loses access pauses, the server is told, and it resumes on its own when access returns. GitHub-wide outages are recognized, not reported as broken trackers.
/track commitsCommit tracking
Every push, in order.
Posts every new commit pushed to the tracked branch, oldest first. Each post names everyone who pushed, linked to their GitHub profile, and links each commit by its short SHA with its message. A long push carries on across up to five posts, and past that the fifth links to the full list on GitHub.
- Every new commit, oldest first
- Commit messages with short-SHA links
- Everyone who pushed, linked to their profile
Options on /track commits
branchPremium- Follow a branch other than the registered one. Run it once per branch to follow several.
ignore_botsPremium- Skip commits by Dependabot, Renovate, and other bot accounts.
ping_rolePremium- Ping a role on each push.
3f9c2a1 Add Apple Pay to checkoutb71e04d Cache product images at the edge09ad5c3 Fix cart total ignoring discount codese5c218f Bump checkout SDK to 4.2/track prsPull requests
Opened, merged, closed, reopened, ready.
Posts when a pull request targeting the tracked branch is opened, merged, closed, reopened, or marked ready for review, with its title, author, source and target branch, status, and a description snippet. Turn on track_reviews to also post review decisions.
- Opened, merged, closed, reopened, and ready for review
- Optional review decisions: Approved and Changes Requested
- Green for open, purple for merged, red for closed
Options on /track prs
track_reviews- Also post review decisions, Approved and Changes Requested only. Off by default.
thread_modePremium- One 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.
branchPremium- Follow a branch other than the registered one.
ignore_botsPremium- Skip bot pull requests and bot reviews.
ping_rolePremium- Ping a role on each post.
feat/apple-pay → main/track issuesLive issue boards
One message that stays current.
One message per repository, edited in place as issues open, close, and change labels, instead of posting new messages. It shows up to 25 open issues with an emoji for their labels, and a Recently Resolved section underneath.
- Edited in place, never a new message per event
- Several repositories can share one board in a channel
- A resolved digest credits whoever closed each issue
Options on /track issues
resolved_embed- Post the resolved digest, which credits whoever closed each issue. On by default for a new board.
labelPremium- A board that shows only one label, such as a bug board in a support channel.
/track workflowsCI/CD workflows
One message per run, live from start to finish.
Posts one message per GitHub Actions run on the tracked branch the moment it is queued or starts, then edits it in place as it runs and when it finishes. The title is the run's status icon and workflow name, linked to the run, with the result and how long it took, the branch, who started it, and the run number underneath.
- Posted when a run starts, updated in place when it ends
- "Succeeded in 1m 32s": the result and the duration
- Yellow while running, green on success, red on failure
Options on /track workflows
detailed_embed- Add the triggering event, the commit, and up to 8 jobs with their results and durations.
failures_onlyPremium- Post only runs that failed, timed out, or failed to start.
branchPremium- Follow a branch other than the registered one.
ignore_botsPremium- Skip bot activity.
ping_rolePremium- Ping a role only when a run fails. The failure posts as a new message, so the ping notifies.
main · theo-builds · push · Run #4823f9c2a1 Add Apple Pay to checkout/track releasesRelease notifications
Announce every ship.
Posts each published release with its name, tag, author, and the start of the release notes. Pre-releases are marked.
- Name, tag, author, and the start of the notes
- Pre-releases marked
- Perfect for #announcements
Options on /track releases
ping_rolePremium- Ping a role on each release.
v2.4.0/track starsStars & forks
Celebrate the momentum.
Posts each new star with the repository's running star total. Turn on track_forks to also post forks, with a link to the new fork.
- Each star with the running total
- Optional fork posts, linking the new fork
- Motivation for open-source communities
Options on /track stars
track_forks- Also post forks, with a link to the new fork. Off by default.
/project createProject boards
A roadmap your community can see.
A status board you update by hand, as one message edited in place. Each entry is one of your tracked repositories, with a status (Planned, Alpha, Beta, Live), a 0 to 100% progress bar, an optional summary, and an optional website link. On Premium, a board can have its own statuses, and an entry can follow a GitHub milestone.
- Grouped Live, Beta, Alpha, then Planned
- 8 progress bar styles, from ▰▱ to ★☆
- Great for public-facing roadmaps
100%100%100%100% 65% 95% 85% 0%/submitissueIssue submission
File GitHub issues from Discord.
Lets members with a role you allow open a real GitHub issue from Discord. They pick a tracked repository, optionally a label, and write a title and description in a form. The issue credits them by Discord name, and a receipt posts in Discord.
- Limited to roles you allow with /submissions roles
- Labels come straight from the repository on GitHub
- Receipts post to a channel you choose with /submissions channels
- Or start one from any message with Create GitHub issue
/settings rate-alertsRate alerts
Never get caught by a quota.
Posts a warning in a chosen channel, pinging up to five roles, when the server's GitHub quota drops below a threshold (50 requests left by default). It posts at most once per quota window, which GitHub resets every hour. Leave out the channel the first time and alerts post where you run the command.
- Your channel and threshold
- Ping up to five roles
- At most once per quota window, and only in your server
Easy to start, hard to break
A guided setup, one place to manage every tracker, and a bot that looks after itself when repositories move or access changes.
/setupGuided setup
One private message walks an admin through linking GitHub, picking a repository, and ticking which trackers post in which channel. Commits, pull requests, and releases are ticked by default, and the channel you run it in is one button press away.
/trackersEvery tracker in one place
Every tracker, grouped by repository, with its channel, branch, filters, label, ping role, and whether it is paused. Pick one to change its options, pause or mute it, move it (one button moves it to the channel you are in), remove it, tidy an issue board, or send a test post that shows the look and permissions are right. A summary on top shows today's GitHub events, the daily average over 7 days, and the busiest repository.
/labels emojiYour own label emoji
Label names always come from the repository on GitHub. You choose the emoji drawn beside each one with /labels emoji, and standard and custom server emoji both work.
Spam protection
A channel that gets more than 12 posts in a minute (30 on Premium) pauses for 5 minutes and posts one notice saying so. Updates during the pause are skipped, not queued, so nothing floods in afterwards, and when it lifts one post counts what was skipped. Issue and project boards keep updating. On Premium, releases, failed runs, and security alerts still post during a pause, up to 60 in one pause.
Trackers that fix themselves
Renamed and transferred repositories are followed automatically. A tracker whose repository was deleted or lost access pauses and the server is told; paused trackers are re-checked every 6 hours and resume on their own. When GitHub is failing for everyone, nothing is paused or reported as broken.
Nothing to rebuild
Removing the bot keeps a server's setup for 90 days, so adding it back restores everything. Uninstalling the GitHub App never deletes trackers either; they resume when access is back.
Comments, deployments, and everything that shapes a feed
Comments, discussions and live issue cards are on every plan. Anything marked Premium needs Premium, and choosing one of its options on Free changes nothing; the bot replies with the upgrade options instead.
/track commentsComments
Posts each new comment on an issue or pull request, and code review comments with the file they are on, with the author and the start of the comment. Comments on an old closed issue post too.
/track discussionsDiscussions
Posts new discussions, replies to them, and when one is marked answered. Delivered by webhook, like comments.
/github issueLive issue cards
/github issue with a number posts a card for that issue or pull request in the channel it is run in: its state (open, draft, merged, closed), author, labels, assignees, milestone, and comment count. The card is edited as those change, within about 15 seconds of GitHub saying so. A card nothing has changed on for 30 days stops updating and stays as it last was. Up to 25 per server, on every plan.
/track deploymentsDeploymentsPremium
On Premium, posts each deployment that succeeds or fails, with its environment, ref, who started it, and a link. Delivered by webhook.
/track securitySecurity alertsPremium
On Premium, posts new Dependabot, code scanning, and secret scanning alerts with their severity and a link. Keep the channel private: an alert names what is vulnerable. A secret's value is never read or posted. Delivered by webhook. Until each account accepts the GitHub App's newer permissions on GitHub, GitHub sends nothing for these alerts.
/filters setFiltersPremium
On Premium, /filters narrows what one tracker posts: files changed on commits, authors, labels on pull requests, workflow names, and words in a message, title, or comment. A filtered update stays hidden however it arrives.
/digest setDigestsPremium
On Premium, /digest set posts a summary of one repository daily or weekly, at an hour you pick in the server's time zone: commits, pull requests merged and opened, issues closed and opened, releases, and workflow runs with what failed. A day with nothing to report posts nothing. It is read from GitHub when it goes out, so no history of activity is stored.
/reminders setRemindersPremium
On Premium, /reminders set posts the pull requests that have gone quiet for stale_days (3 by default) and the ones waiting for review, on a schedule, optionally pinging a role. Drafts don't count, and with nothing to report it posts nothing. /reminders queue shows the same list privately, right now.
/track prsPull request cardsPremium
On Premium, with thread_mode, each pull request is one message, edited in place as it opens, merges, or closes. Under it, a thread collects its reviews, CI results, comments, and new commits. The thread needs Create Public Threads and Send Messages in Threads. Without them, what would go in the thread posts in the channel. The Cards and threads button in /trackers switches it on, and Comment on GitHub turns a message in the thread into a comment on the pull request.
/settings actions-roleButtons on postsPremium
On Premium, a failed workflow run has a Re-run failed jobs button, and its post updates when the re-run finishes. Comments on issues and /submitissue receipts have Close issue and Add label. Managers can use them, and so can a role set with /settings actions-role. They act on GitHub as the GitHub App, so the server decides who may press them. Who pressed is said in the channel, and a closed issue gets a comment naming them. Re-running needs the app's Actions permission, which each account has to accept on GitHub.
Apps > Comment on GitHubComment on GitHubPremium
On Premium, right-click a message in a pull request's thread, then Apps > Comment on GitHub, and a form opens with that message's text to edit. Sending it posts a comment on the pull request as the GitHub App, signed with your Discord name, and the thread says who commented. It is for the same people as the buttons on posts: managers, and the role set with /settings actions-role. @mentions in it don't notify anyone on GitHub.
/mygithubMentions and DMsPremium
On Premium, a member connects their GitHub account with a Sign in with GitHub button, through /mygithub. Once connected, posts really @mention them: when their review is requested, when their pull request gets a review decision, when a run they started fails, and when a comment by one of the repository's owners, members, or collaborators mentions their GitHub username, so strangers can't ping them. A Turn on DMs button adds a DM for those same moments, for that member only, at most 30 an hour. ForgeFeed reads their username and account number and keeps nothing else, so a renamed account keeps its mentions.
/contributors leaderboardContributorsPremium
On Premium, ForgeFeed counts commits on the registered branch, pull requests opened and merged, and reviews and issues closed, per GitHub account and repository, from when the server has Premium. Bots don't count, nor does reviewing your own pull request. /contributors leaderboard shows the top 10, /contributors card shows one person's numbers, and /contributors weekly posts the week's top contributors without pinging anyone. Roles can be given once a member reaches a number, but never one that can moderate or manage the server.
/stats ciCI insightsPremium
On Premium, workflow trackers keep count of each workflow's runs. A failed run says when it is one of several in a row, and a run that only passed on a retry says it may be flaky. When a failing workflow passes, ForgeFeed posts that it is green again, even on a tracker showing only failures. /stats ci shows each workflow's pass rate, usual run time, flaky passes, and current streak, counted from when tracking started. Cancelled and skipped runs don't count. The Insights button in /trackers turns it off for one tracker.
/repo brandBrandingPremium
On Premium, /repo brand gives one repository's posts their own color, a hex color such as #5865F2, and a layout: compact, standard, or detailed. Red for failures and purple for merges stay, so they keep their meaning. The bot's name and avatar stay ForgeFeed's.
/track bulkBulk setup and templatesPremium
On Premium, /track bulk turns on what you pick for every repository the server tracks, or with scope for everything the linked accounts can reach, as far as the plan goes, in one channel. /track template tracks new repositories on their own: when one is created on a linked account, or granted to the app, it is registered and gets what the template says, in the template's channel. On an organization, a new repository waits until someone confirms it on the link page. The alerts channel hears about each one.
/project milestoneMilestone project boardsPremium
On Premium, /project milestone adds an entry that follows a GitHub milestone: its progress is how many of its issues are closed, it shows the count and the due date, and its status moves up the board's list as it fills. It updates when an issue or the milestone changes, and every 15 minutes in any case. /project statuses gives a board its own statuses, two to ten of them.
Premium
Everything marked Premium, for the whole server
From $4.99 a month for 10 repositories. Organizations and more accounts, deployments and security alerts, filters, digests, reminders, Comment on GitHub, and every Premium option. Bought in Discord, and nothing is deleted if it ends.
Pause, mute, and find out why nothing posts
Every tracker can be paused, muted or sent a test post, /doctor explains anything that isn't posting, and each server sets its own quiet hours, time zone, manager role and alerts channel.
/trackersPause and mute
Pause a tracker until you resume it, or mute it for an hour, 8 hours, 24 hours or a week. Updates in that time are skipped, not saved up.
/trackersSend test post
Posts the repository's latest update of that kind in the tracker's channel, built the way the tracker builds it, so you see the look and the permissions are right without waiting for activity. The reply to /track has the same button.
/doctorWhy nothing posts
Checks each linked account, repositories against the plan's limit, every tracker that can't post and why, whether the webhook endpoint is up, and the last event GitHub sent.
/settings quiet-hoursQuiet hours
Pick hours, 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.
/settings timezoneTime zone
Sets the time zone digests, reminders and weekly leaderboards count their hours in. It defaults to Eastern. Posts and boards show when they were made in each reader's own time zone.
/settings manager-roleManager role
A role that can run ForgeFeed without Manage Server. Discord only shows these commands to Manage Server by default, so allow the role under Server Settings > Integrations > ForgeFeed.
/settings alerts-channelAlerts channel
Where notices about the bot go, such as a paused tracker or a plan change. They name repositories and channels, so pick somewhere the team can see. Without one, they go to the owner by DM.
Apps > Create GitHub issueCreate GitHub issue
Right-click a message, or long-press on mobile, to open a GitHub issue with its text filled in and a link back to the message. Attachments are not carried over. Roles you allow can use it, on every plan.
/planYour plan
The plan, repositories used against the limit, and active tracker counts. On Free it lists what Premium adds, with Discord's upgrade buttons and a link to the store.
What ForgeFeed looks after without a command
A tracker keeps working when the repository around it changes, and the bot tells the owner when something needs a decision.
- 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.
Keep reading
- Use casesSee each tracker doing a real job, from CI/CD alerts to a public roadmap board.
- PricingFree has every tracker type except deployments and security alerts. Premium adds those, organizations, more repositories, and the options marked Premium.
- Slash command referenceThe command for each tracker, the options it takes, and the permissions it needs.
Turn on the feeds that fit your team.
Start on Free with one repository. Point commits at #dev, releases at #announcements, and CI at #builds. Each tracker picks its own channel.
Need organizations or more repositories? Premium, from $4.99 a month for 10 repositories
Join the Discord servers already running ForgeFeed.