docs(readme): add Telegram to Communication integrations#1902
Conversation
Telegram has shipped (docs/messaging/telegram.mdx, integrations-overview.mdx, docs.json nav) but was missing from the README integrations matrix. Fixes Tracer-Cloud#1014
Greptile code reviewThis repo uses Greptile for automated review. Before merge, aim for Confidence Score: 5/5 with zero unresolved review threads — see CONTRIBUTING.md. Run a review — add a PR comment with: Give it ~5-10 minutes (sometimes longer) for results, then fix feedback and re-trigger until you reach Confidence Score: 5/5. Optional: automate with the greploop skill. |
Greptile SummaryThis PR adds Telegram to the Communication row of the README integrations matrix, bringing it in sync with the rest of the codebase where Telegram support is already fully implemented (docs, nav, app code).
Confidence Score: 5/5A single-line README addition with no logic changes — safe to merge. The change adds one word to a Markdown table, matching the exact style already used by the adjacent Discord and Google Docs entries (no icon, · separator). The Telegram integration is verified present across every other doc surface the PR description enumerates, so no functional gap is introduced. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Telegram integration shipped] --> B[docs/messaging/telegram.mdx ✅]
A --> C[docs/integrations-overview.mdx ✅]
A --> D[docs.json nav ✅]
A --> E[app/integrations/verify.py ✅]
A --> F[app/cli/constants.py ✅]
A --> G[README.md Communication row ❌ before PR]
G --> H[README.md Communication row ✅ after PR]
Reviews (1): Last reviewed commit: "docs(readme): add Telegram to Communicat..." | Re-trigger Greptile |
|
⚡ LGTM → Merged. @0xDevNinja, your work is in. Every commit counts — thank you for this one.
👋 Join us on Discord - OpenSRE : hang out, contribute, or hunt for features and issues. Everyone's welcome. |
…d#1902) Telegram has shipped (docs/messaging/telegram.mdx, integrations-overview.mdx, docs.json nav) but was missing from the README integrations matrix. Fixes Tracer-Cloud#1014
Fixes #1014
Describe the changes you have made in this PR -
Adds Telegram to the Communication row of the integrations matrix in
README.md.Telegram delivery already shipped end-to-end (
docs/messaging/telegram.mdx, listed indocs/integrations-overview.mdx, present indocs.jsonMessaging nav, supported by_SUPPORTED_TARGETSinapp/integrations/verify.pyandVERIFY_SERVICESinapp/cli/constants.py), but the README matrix still listed onlySlack · Google Docs · Discord. Per @muddlebee's direction on the issue ("you can tackle this, ensure its placed at correct docs"), the only doc surface still out of sync is the README row.Demo/Screenshot for feature changes and bug fixes -
Before:
**Communication** | Slack · Google Docs · DiscordAfter:
**Communication** | Slack · Google Docs · Discord · TelegramCode Understanding and AI Usage
Did you use AI assistance (ChatGPT, Claude, Copilot, etc.) to write any part of this code?
Explain your implementation approach:
The issue (and PR #1023 history) flagged that Telegram docs were missing. I traced the doc surfaces:
docs/messaging/telegram.mdx— already present.docs/integrations-overview.mdxline 23 — already mentions Telegram alongside Slack/Discord.docs.jsonnav — Telegram already wired into the Messaging group.README.mdintegrations matrix line 219 — the only remaining surface where Telegram was missing.So this is a one-line README addition rather than a full new doc page. Discord and Google Docs were already on the row, so Telegram just slots in next to them. No icon image used because the existing Discord and Google Docs entries also have no icon — kept the row consistent.
Checklist before requesting a review