RhenCloud bd7a8f2632 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.		2026-08-03 05:19:05 +08:00
..
actions.md	docs: document admin groups, OAuth redirect, and API renames	2026-08-03 00:33:18 +08:00
oauth.md	feat: migrate send logs and discord links to D1	2026-08-03 05:18:58 +08:00
overview.md	feat: add Telegram push support with multi-target routes	2026-08-03 05:19:05 +08:00