Skip to content

feat: add reusable Telegram notification workflows - #139

Merged
ineedjet merged 1 commit into
mainfrom
feat/telegram-notification-workflows
Aug 12, 2026
Merged

ineedjet merged 1 commit into
mainfrom
feat/telegram-notification-workflows

Conversation

@ineedjet

@ineedjet ineedjet commented Aug 12, 2026 •

Copy link
Copy Markdown
Contributor

🤖 [rubykatzen/baseline]:

Add separate reusable Telegram workflows for pull request and issue activity.

  • notify PR opened, ready, reopened, and merged events;
  • send a scheduled digest of up to ten open non-draft PRs;
  • provide optional issue-closure notifications with caller-owned filtering;
  • use dedicated PR-message preparation, issue-message preparation, and generic
    Telegram delivery actions;
  • pass Telegram secrets explicitly and allow callers to map different channels;
  • avoid logging successful Telegram API responses;
  • retire the redundant unreleased-commit notification now represented by
    Release Please PRs;
  • add formatter, routing, and boundary tests plus consumer documentation.

Part of #117. Also addresses the Baseline side of #99.

🔔 🧹 ✅

@ineedjet
ineedjet force-pushed the feat/telegram-notification-workflows branch 8 times, most recently from 436be30 to 56527b9 Compare August 12, 2026 15:09
@ineedjet
ineedjet force-pushed the feat/telegram-notification-workflows branch from 56527b9 to 0612a0b Compare August 12, 2026 15:10
@ineedjet
ineedjet enabled auto-merge (squash) August 12, 2026 15:15
@ineedjet
ineedjet merged commit c3bd9f7 into main Aug 12, 2026
5 checks passed
@ineedjet
ineedjet deleted the feat/telegram-notification-workflows branch August 12, 2026 15:16
This was referenced Aug 12, 2026
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