mirror of
https://github.com/ReCloudStudio/WebHooker.git
synced 2026-09-22 16:11:29 +00:00
RhenCloud
bd7a8f2632
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.
23 lines
564 B
Text
23 lines
564 B
Text
# GitHub
|
|
GITHUB_WEBHOOK_SECRET=your-webhook-secret
|
|
GITHUB_APP_ID=your-app-id
|
|
GITHUB_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----\n...\n-----END RSA PRIVATE KEY-----"
|
|
GITHUB_CLIENT_ID=your-client-id
|
|
GITHUB_CLIENT_SECRET=your-client-secret
|
|
|
|
# Discord
|
|
DISCORD_TOKEN=your-bot-token
|
|
DISCORD_PUBLIC_KEY=your-public-key
|
|
DISCORD_APPLICATION_ID=your-application-id
|
|
DISCORD_CHANNEL_ID=your-channel-id
|
|
|
|
# Telegram
|
|
TELEGRAM_TOKEN=your-bot-token
|
|
TELEGRAM_WEBHOOK_SECRET=your-webhook-secret
|
|
|
|
# Server
|
|
PORT=3000
|
|
BASE_URL=http://localhost:3000
|
|
|
|
# Config
|
|
CONFIG_PATH=./config.yaml
|