Reseam Relay

Posts what happens on git.reseam.app and in the Reseam API to Reseam's socials. One Forgejo org webhook sends every event here, the API sends new announcements and requests, and Relay fans them out:

• Everything. Pushes, tags, issues, pull requests, reviews, comments, wiki edits, packages and CI runs, to Discord and Telegram.
• Releases and announcements. Published releases of the repositories listed in config.toml, and announcements from the API, to Discord, Telegram, Reddit and X. Posts link to the entry's page on reseam.app.
• Requests. New patch requests from the API, to a Discord moderation channel.

A release is posted once the repository's index (patches.json, manager.json) lists it, so the link and Reseam Manager already show it. Relay checks every 20 seconds and posts anyway after 15 minutes. A release whose notes have no feat, fix or perf line counts as maintenance.

Events from private repositories are always dropped. That includes a fork into or out of one, CI runs, and packages without a repository.

Configure

config.toml decides what goes where:

[everything]
exclude = []                         # repositories left out of the everything feed

[releases]
prereleases = ["discord", "telegram"]  # targets that also announce prereleases
maintenance = ["discord", "telegram"]  # targets that also announce maintenance releases

[releases.repos."reseam/patches"]
name = "Reseam Patches"                              # name used in posts
index = "https://api.reseam.app/patches.json"        # must list the release before it is posted
page = "https://reseam.app/updates/patches/{version}/"  # link in posts

[api]
announcement_page = "https://reseam.app/updates/news/{id}/"
request_page = "https://reseam.app/requests/?id={id}"

Credentials come from the environment (see .env.example). WEBHOOK_SECRET is required. Each target turns on when all of its variables are set:

Target	Variables
Discord	DISCORD_FEED_WEBHOOK, DISCORD_RELEASES_WEBHOOK, DISCORD_REQUESTS_WEBHOOK (moderation channel)
Telegram	TELEGRAM_BOT_TOKEN with TELEGRAM_FEED_CHAT / TELEGRAM_RELEASES_CHAT, optional *_THREAD for a forum topic
Reddit	REDDIT_CLIENT_ID, REDDIT_REFRESH_TOKEN, optional REDDIT_CLIENT_SECRET, REDDIT_SUBREDDIT (default reseamapp)
X	X_AUTH_TOKEN, X_CT0: cookies of a logged-in x.com session

Reddit posts go through an installed app (redirect uri http://localhost:8080, no secret), which any account can authorize. Run REDDIT_CLIENT_ID=... bun scripts/reddit-auth.ts, open the printed link while logged in as the posting account, and set the printed REDDIT_REFRESH_TOKEN. The account must be allowed to post in the subreddit.

X posts go through the x.com web API with bird, not the paid API. Each request carries an x-client-transaction-id signed the way the x.com web app does it (x-client-transaction-id); with bird's random one, X rejects posts as automated (error 226). Posting stops when the session cookies expire or X changes its web client.

GET /v1/health lists the targets that are on.

Reseam API

The API posts new announcements and requests to POST /v1/api, signed like a Forgejo webhook: X-Reseam-Signature is the hex HMAC-SHA256 of the body. Set the same secret as API_SECRET here and RELAY_SECRET on the API, and point the API's RELAY_URL at Relay.

Forgejo webhook

Add one webhook on the reseam organization:

• Type Forgejo, URL https://<host>/v1/forgejo, content type JSON
• Secret: the value of WEBHOOK_SECRET
• Trigger on all events

Relay answers 202 right away and posts afterwards, because Forgejo stops waiting after a few seconds. Each target posts in order and waits out rate limits. A failed post is logged and not retried.

Develop

Needs Bun.

bun install
WEBHOOK_SECRET=dev bun run dev  # server on port 4100
bun run typecheck

Built with Bun and Elysia.