Skip to content

Add teleping – Node.js production alerts via Telegram#202

Open
yerdaulet-damir wants to merge 1 commit into
ebertti:masterfrom
yerdaulet-damir:add-teleping
Open

Add teleping – Node.js production alerts via Telegram#202
yerdaulet-damir wants to merge 1 commit into
ebertti:masterfrom
yerdaulet-damir:add-teleping

Conversation

@yerdaulet-damir
Copy link
Copy Markdown

What

Adds teleping to the Tools section.

Why it fits

teleping is a Node.js/TypeScript npm package that sends structured production alerts to Telegram — signups, errors, metrics, deploys. Built specifically for developers who use Telegram as their operations channel.

Features:

  • Structured messages with separators, emojis, and context fields
  • Smart batching (50 identical events → 1 message)
  • Quiet hours (suppress non-critical alerts at night, errors always go through)
  • Components: card, progress bar, table, checklist
  • Zero dependencies, 1 import
  • CLI: npx teleping init for guided setup

A natural addition to the Tools section alongside telegram-send and telegram-owl.

Checklist

  • Added to bottom of Tools section
  • Format: * [Name](url) – Description (matching existing entries)
  • No duplicate
  • Meaningful PR title (not "Update readme.md")

Copy link
Copy Markdown
Contributor

@devloai devloai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary:

  • Adds teleping, a Node.js/TypeScript npm package for sending structured production alerts to Telegram.
  • Entry is placed at the bottom of the Tools section as required.
  • PR title is meaningful and descriptive.

Review Summary:

The entry is legitimate — the GitHub repo is public and accessible, the tool is functional with a clear Telegram use case, and there are no duplicates in the list. Format is mostly correct (en dash separator , description starts with a capital letter and ends with a period, bullet point syntax). One minor punctuation inconsistency was flagged: the description uses both (en dash) as the link separator and (em dash) within the description itself, which should be unified for clean formatting.

Suggestions

  • Fix the mixed dash punctuation in the description by applying the suggestion in the review comment. Apply

Comment thread README.md
* [telegram-finder](https://www.telegram-finder.io) - Find Telegram users from phone, email, or LinkedIn URL, via web app or API.
* [Telegram Media Downloader](https://github.com/rfsbraz/telegram-downloader) – Self-hosted daemon that automatically downloads media from Telegram channels, groups, and forum topics.
* [telepipe](https://github.com/Linuxmaster14/telepipe) – Lightweight Bash utility for piping command output to Telegram chats. Automatically switches between message and file modes based on content length.
* [teleping](https://github.com/yerdaulet-damir/teleping) – Production observability for Node.js/TypeScript: structured alerts, smart batching, quiet hours, and components (card/table/progress/checklist) — zero dependencies.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description mixes two different dash characters: (en dash) as the separator after the link, then (em dash) before "zero dependencies". For consistency, the inner dash should match or be replaced with a simple comma or semicolon.

Suggested change
* [teleping](https://github.com/yerdaulet-damir/teleping) – Production observability for Node.js/TypeScript: structured alerts, smart batching, quiet hours, and components (card/table/progress/checklist) zero dependencies.
* [teleping](https://github.com/yerdaulet-damir/teleping) – Production observability for Node.js/TypeScript: structured alerts, smart batching, quiet hours, and components (card/table/progress/checklist); zero dependencies.
actions

Feedback: Rate this comment to help me improve future code reviews:

  • 👍 Good - Helpful and accurate
  • 👎 Poor - Wrong, unclear, or unhelpful
  • Skip if you don't have any strong opinions either way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant