You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
issue_comment.created is not handled. Comments on issues and PRs — often where real blockers or questions surface — currently produce no Telegram notification.
Background
The webhook subscription list in the README (setup step 5) only mentions Issues, Pull requests, Workflow runs, and Deployment statuses. src/github/webhooks.ts has no issue_comment handler at all. A question or "blocked on X" comment left on a PR is invisible until someone happens to check GitHub.
Proposed Solution
Add a webhooks.on("issue_comment.created", ...) handler. Use payload.issue.pull_request presence to distinguish "comment on a PR" from "comment on an issue" and label the notification accordingly, reusing the existing link/icon helpers in formatters.ts.
Technical Scope
src/github/webhooks.ts — new handler
src/github/formatters.ts — new formatCommentEvent
README.md — add "Issue comments" to the webhook subscription list
Tests: formatter unit test for both issue-comment and PR-comment cases
Acceptance Criteria
New comments on issues produce a notification distinct from comments on PRs
Comment body is truncated/escaped safely (reuse escapeHtml) before posting
Unit tests added
README updated
CI passes
Code follows project conventions
Edge Cases
Very long comment bodies — must be truncated to a reasonable preview length before posting to Telegram
Comments containing HTML-significant characters must be escaped (reuse src/utils/html.ts)
Bot-authored comments (e.g. from other automation) — consider whether to filter these out to avoid notification loops
Risks
Highest noise-per-event of any handler in this backlog on an active repo — should ship alongside or after issue Add issue and PR comment notifications #6 (label-based filtering) to avoid flooding the channel
No structural risk to existing handlers
Deliverables
Feature implementation
Unit tests
README update
Labels
enhancement, backend
Priority
Medium — real value, but noise risk means it should land with filtering in place.
Summary
issue_comment.createdis not handled. Comments on issues and PRs — often where real blockers or questions surface — currently produce no Telegram notification.Background
The webhook subscription list in the README (setup step 5) only mentions Issues, Pull requests, Workflow runs, and Deployment statuses.
src/github/webhooks.tshas noissue_commenthandler at all. A question or "blocked on X" comment left on a PR is invisible until someone happens to check GitHub.Proposed Solution
Add a
webhooks.on("issue_comment.created", ...)handler. Usepayload.issue.pull_requestpresence to distinguish "comment on a PR" from "comment on an issue" and label the notification accordingly, reusing the existing link/icon helpers informatters.ts.Technical Scope
src/github/webhooks.ts— new handlersrc/github/formatters.ts— newformatCommentEventREADME.md— add "Issue comments" to the webhook subscription listAcceptance Criteria
escapeHtml) before postingEdge Cases
src/utils/html.ts)Risks
Deliverables
Labels
enhancement, backend
Priority
Medium — real value, but noise risk means it should land with filtering in place.
Estimated Completion: 96 hours
Telegram: https://t.me/txioCommunity