5 commits

Author	SHA1	Message	Date
RhenCloud	aec0d1a257	feat: add gitea/forgejo support	2026-08-11 22:01:04 +08:00
wyf9	afe19795b1	docs: sync documentation with current codebase ... - Update event formatter count 23 -> 28 (add ping, workflow_job, status, deployment, check_suite) - Document Telegram support end-to-end (routes, /gh commands, richheader, secrets) - Fix route schema to use targets array and group fields (owners, emoji) - Correct KV/D1 storage layout (msg:*, i18n:*, D1 links/send_logs) - Note GITHUB_APP_ID/GITHUB_PRIVATE_KEY are unused; drop legacy DISCORD_CHANNEL_ID/PORT/CONFIG_PATH - Remove stale Docker deployment section - Update color table, branch filter compatibility, admin API endpoints - AGENTS.md: add Documentation section requiring doc updates after functional changes	2026-08-05 17:22:15 +08:00
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
RhenCloud	d540d465d1	refactor: replace Discord Gateway DO with Interaction Endpoint	2026-08-03 03:02:42 +08:00
RhenCloud	512d4b01d5	initial commit	2026-07-24 21:48:50 +08:00