basically the project linked above, but slightly rewritten to run with deno.

public instance available at https://gh-webhook.minibomba.pro/

mostly the same

POST /{channel ID}/{webhook token} - Execute webhook
(also POST /api/webhooks/{channel ID}/{webhook token}/github for maxium compatibility with discord)

/ - Redirects to this repository
/version - Sends currently deployed git hash
/source - Redirects to a view of the currently deployed commit

grab a discord webhook, replace discord.com with gh-webhook.minibomba.pro, give it to github, don

to run outside of a container: deno run --allow-net=0.0.0.0:8000,discord:443 --allow-read=./.git --allow-env='GWE_*' main.ts

to run inside a container: simply build the provided Dockerfile and run the image - all required params are passed in by default

the server will listen on 0.0.0.0:8000 by default

this script looks at 3 different env vars to determine where it should listen for connections:

• GWE_LISTEN_UNIX - if set, it will listen on this path as a unix socket
• GWE_LISTEN_PORT - can override the default 8000 port
• GWE_LISTEN_HOST - can override the default 0.0.0.0 address

these variables affect the listen address in the following way:

• if GWE_LISTEN_UNIX is set, the server will expose the specified unix socket
• if GWE_LISTEN_PORT or GWE_LISTEN_HOST is set, the server will expose the specified tcp port
• if neither of these variables are set, the server will expose the default 0.0.0.0:8000 tcp port
• setting both GWE_LISTEN_UNIX and any of the variables responsible for the tcp socket will result in the server listening both on a unix and tcp socket

• network discord:443, read ./.git and env GWE_* is always required
• if the server is set to listen on a tcp socket, network <host>:<port> must be granted
• if the server is set to listen on a unix socket, read and write for the socket path must be granted

i've recently have been encountering issues with cloudflare workers IPs getting blocked by discord, causing dropped messsages. so i decided to slightly restructure the project to allow it to be run with deno, which has the closest http server api to cf workers.

discord's github webhook support isn't great. it doesn't attach release descriptions to messages about them being created, it can't differentiate between a PR getting closed and it getting merged, it doesn't know about the different issue close reasons. it really feels like no discord dev had touched that area in years - it feels outdated and unfinished.

this project can currently intercept and improve the following events:

• release creation
  • adds the release description and timestamp into the message
  • updates the message if the release is edited within 15 minutes of publishing
• issue closing/reopening
  • includes the reason for closing the issue (completed/not planned)
  • adds colors associated with the different close reasons and reopening the issue
• pull requests
  • differentiates between closing and merging the PR
  • sends messages when a PR is marked as draft or ready for review
  • adds colors associated with these actions
  • blocks "Pull request review submitted" events when someone comments on a review
    • review comment content will still be sent to discord if pull_request_review_comment event is enabled. this simply removes the noise
  • merges "New review comment" into "Pull request review submitted" events for initial comments on a review thread
    • you'll get a single message with the main review content and + 20 comments instead of 21 messages
• merge queues
  • sliences merge queue bot's pushes and branch creations
  • sends messages when automatic merge is enabled or disabled for a PR
  • sends messages when a PR is added or removed from the merge queue

this project is licensed under MIT.

note that major parts of this project are simply copied from github-webhook-proxy (which is also my project) - this is why the license file has a date of 2022 despite the git history starting in 2025.