ReCloudStudio/WebHooker
1
0
Fork 0
mirror of https://github.com/ReCloudStudio/WebHooker.git synced 2026-09-22 16:11:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

feat: add Telegram push support with multi-target routes

Browse source 
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 2026-08-03 05:17:59 +08:00
parent dcbe93be91
commit bd7a8f2632
No known key found for this signature in database
GPG key ID: A574A617378C4E0B
39 changed files with 1165 additions and 162 deletions
Download patch file Download diff file Expand all files Collapse all files

4
src/__tests__/admin.test.ts
View file

@ -52,7 +52,7 @@ const sampleRoutes: Route[] = [
name: "Backend PRs",
enabled: true,
filters: [{ type: "event", match: "pull_request" }],
target: { channelId: "111" },
targets: [{ channelId: "111" }],
},
];
@ -133,6 +133,6 @@ describe("config routes persistence", () => {
const second = await loadConfig(env);
expect(second.routes).toHaveLength(1);
expect(second.routes[0]!.id).toBe("backend-prs");
expect(second.routes[0]!.target.channelId).toBe("111");
expect(second.routes[0]!.targets[0]!.channelId).toBe("111");
});
});