feat: add Telegram push support with multi-target routes

Add a platform-aware route target system so a single route can forward
to several destinations at once (e.g. a Discord channel and a Telegram
group). Route.target becomes Route.targets[] with per-entry platform,
channelId/threadId for Discord and chatId/topicId for Telegram; the
legacy single-target format is normalized on load and accepted by the
admin API.

Implement the Telegram driver with HTML rendering and Bot API
sendMessage (chat_id + message_thread_id for topics, retry on 429/5xx),
plus /gh commands served over POST /telegram/webhook: login, logout,
comment, merge and close. The comment/merge/close commands resolve the
issue or PR from the replied-to notification message. OAuth binding now
stores a D1 telegram_links mapping and replies with a confirmation.

Sync the Telegram webhook from the scheduled trigger via setWebhook.
This commit is contained in:
RhenCloud committed 2026-08-03 05:19:05 +08:00
1 parent dcbe93be91
commit bd7a8f2632
39 files changed
+1165 -162

No files matched your search

+2
View File
@@ -4,6 +4,7 @@ import { verifySignature } from "./events/verify";
import { parseEvent } from "./events/parse";
import { dispatchEvent } from "./core/dispatch";
import { handleInteractionRequest } from "./drivers/discord/interactions";
import { handleTelegramWebhookRequest } from "./drivers/telegram/updates";
import { createOAuthRoutes } from "./web/oauth-routes";
import { createActionRoutes } from "./web/action-routes";
import { createAdminRoutes } from "./web/admin-routes";
@@ -71,6 +72,7 @@ export function createServer(): Hono<{ Bindings: Env }> {
});
app.post("/discord/interactions", (c) => handleInteractionRequest(c.req.raw, c.env));
app.post("/telegram/webhook", (c) => handleTelegramWebhookRequest(c.req.raw, c.env));
app.notFound((c) => {
if (c.env.ASSETS) {