blob: 788eb0567cde02027b3cd14ce108ede26b1a883a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
# Telegram Integration Scripts
This directory contains scripts for integrating with Telegram for sending notifications and messages.
## Scripts
### 📨 `send_telegram_message.py`
General-purpose script for sending messages or file contents to Telegram channels.
**Features:**
- Send text messages or file contents
- Support for message threads
- Message chunking for large content
- Disable web page previews
- Configurable delays between messages
**Documentation:** [README_telegram.md](README_telegram.md)
### 👥 `parse_and_send_team_issues.py`
Specialized script for parsing GitHub issues and sending team-specific notifications. Supports two modes: immediate updates and periodic trend reports.
**Features:**
- **On-Mute-Change Updates**: Parse team issues from formatted results and send immediate notifications
- **Periodic Trend Updates**: Send weekly/monthly trend reports with statistics and charts
- Support for multiple responsible users per team
- Team lead mentions in messages
- Support for message threads
- Dry run mode for testing
- Automatic team discovery from YDB data
- Fallback to default channel for teams without specific configuration
**Documentation:** [README_parse_and_send.md](README_parse_and_send.md)
### 🚨 `alert_queued_jobs.py`
Monitors the GitHub Actions queue and sends Telegram alerts when jobs are stuck (PR-check, Postcommit, etc.). Runs in **`.github/workflows/telegram_scheduled_notifications.yml`** (job **CI queue Telegram alerts**; same file also runs **Mute digest to Telegram** via `send_digest.py`).
**Documentation:** [README_alert_queued_jobs.md](README_alert_queued_jobs.md) — vars/secrets, thresholds, local testing (dry-run), CLI.
## Configuration
### Example Team Responsible Mapping
See [team_leads_example.json](team_leads_example.json) for example configuration.
**Supported formats:**
- Single responsible: `"team": "@team-lead"`
- Multiple responsible: `"team": ["@lead1", "@lead2", "@lead3"]`
## GitHub Actions Setup
### 1. Secrets (Settings → Secrets and variables → Actions → Secrets)
- `TELEGRAM_BOT_TOKEN` - your bot token
- `TELEGRAM_YDBOT_TOKEN` - YDB bot token (used in workflow)
### 2. Variables (Settings → Secrets and variables → Actions → Variables)
- `TELEGRAM_MUTE_CHAT_ID` - channel ID in format "chat_id/thread_id" (e.g., "2018419243/1")
- `TEAM_TO_RESPONSIBLE_TG` - JSON string mapping teams to responsible users
### 3. Getting Bot Token
1. Find [@BotFather](https://t.me/BotFather) in Telegram
2. Send `/newbot`
3. Follow instructions to create a bot
4. Get token like `123456789:ABCdefGHIjklMNOpqrsTUVwxyz`
### 4. Getting Channel ID
For channel `https://t.me/c/2018419243/1`:
- Channel ID: `-1002018419243`
- Or use [@userinfobot](https://t.me/userinfobot) to get the ID
## Usage in GitHub Actions
These scripts are used in the `create_issues_for_muted_tests.yml` workflow to send notifications about muted tests to team channels.
## Requirements
- Python 3.7+
- `requests` library
- Valid Telegram bot token
- Telegram chat/channel access
|
