Use case
GitHub commit notifications in Discord
Every push to your tracked branch, posted to Discord as a clean embed the moment it lands.
/postcommits
The problem
Your team lives in Discord but commits happen on GitHub. Flipping between the two means activity gets missed, and the built-in webhook dumps raw payloads into a single channel with no grouping.
How ForgeFeed solves it
- An embed on every push, up to 25 commits grouped by author
- Commit messages with short-SHA links back to GitHub
- Point it at a dedicated #dev or #activity channel
- Event-driven, so quiet repos stay quiet
dev-activity
Search
ForgeFeedApp6/25/2026 9:29 AM
GitHub
New Updates for Discord GitHub Bot
Developer
chrislenga
Changes (5)
• feat(db): add consecutive_failures and disabled_at to commit_trackers schema
• feat(db): migrate commit_trackers with failure-tracking columns
• feat: pause commit trackers after repeated 404/403 and recreate raced issue boards
• feat: clear commit tracker pause state when re-added via /postcommits
• fix: delay welcome DM 5s so Discord can register the shared guild
Posted: 06-25-2026 09:29 AM EST
FAQ
Questions, answered
How many commits show per push?
Up to 25 commits per push, grouped by author and chunked into readable blocks. Larger pushes are summarized so the embed never overflows.
Can I send commits from different repos to different channels?
Yes. Each commit tracker targets its own channel, so one repo can post to #dev while another posts to #backend.
Bring your GitHub activity into Discord.
Set up in minutes with slash commands. Free for a personal project, Premium when you scale to organizations.
Join the 35+ Discord servers already running ForgeFeed.