Your GitHub commits,
delivered straight to Discord.
Connect a repository in under a minute. Every push arrives as a clean embed with the author, branch, file stats, and a link to the commit.
One-page setup
Connect a repository
How it works
Three steps. Then it's out of your way.
No installs, dashboards, or bot commands. You paste one URL into GitHub and close the tab.
Paste a Discord webhook
Create a webhook in the channel you want, then paste the URL. It is encrypted before it touches the database.
Choose your timezone
Search any zone in the world. Commit timestamps and footer dates follow daylight saving automatically.
Connect one GitHub URL
Add the generated endpoint to your repo. Signatures, stats, and delivery are handled from there.
Under the hood
The interesting parts, handled.
A focused FastAPI service receives the push, verifies it, fetches exact stats, and builds the embed with discord.py. PostgreSQL keeps every setup independent.
Signed before parsed
Every delivery is verified with HMAC-SHA256 before the payload is read.
Retries don't duplicate
Delivery IDs and commit SHAs are recorded, so GitHub retries stay idempotent.
Stats from the source
Additions, deletions, and modified files come from GitHub's commit API.
Secrets stay secret
Discord URLs are Fernet-encrypted; endpoint tokens are stored as one-way hashes.
FAQ
The obvious questions.
A small tool should explain itself. If something is still unclear, the API docs are one click away.
Read the API docsDo I need to install a Discord bot?
No. You create an incoming webhook in Discord, paste it here, and the server posts embeds to that webhook. There is no bot user to invite and no slash command to set up.
How is my Discord webhook stored?
It is encrypted at rest with Fernet using a server-side key. The generated GitHub endpoint contains only a random, hashed identifier — never your Discord URL. The API never returns the stored URL after setup.
What happens if GitHub retries a delivery?
Each X-GitHub-Delivery ID is claimed once, and each repository, branch, and commit SHA is tracked separately. Successful embeds are skipped on retry, while failed deliveries can try again.
Can I use one endpoint for multiple repositories?
Yes. Add the same payload URL and secret to as many repositories as you like. Every repository and branch is processed independently, and the embed always shows the real repo name.
How do I turn notifications off?
Delete the webhook in GitHub, delete the incoming webhook in Discord, or use the Delete setup control shown after generating your endpoint. GitHub deliveries stop immediately.