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
{{ message }}
Repository navigation
Consolidate Telegram PR and issue notifications in Baseline #117
Move pull request and issue Telegram notifications into Baseline and export independent reusable workflows. PR notifications are a baseline repository capability; issue notifications are optional and may use a different Telegram channel.
Implemented
Added notify-telegram-pr-shared.yml for opened, reopened, ready, merged, and scheduled open-PR notifications.
Added notify-telegram-issue-shared.yml for closed-issue notifications.
Split PR preparation, issue preparation, and generic Telegram delivery into dedicated internal actions.
Added Baseline own PR notification caller using a local shared-workflow reference.
Passed TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID explicitly.
Kept issue filtering and channel selection in consumer callers.
Tested routing, draft and merge filtering, formatting, digest limiting, and empty digest behavior.
Documented both reusable workflows.
Retired the unreleased-commit digest because Release Please exposes release readiness as an open pull request.
Releaser cleanup belongs to the planned Releaser archival and is intentionally outside this issue.
Existing Releaser issues will be reviewed and closed independently.
Result
Baseline now owns independent reusable PR and issue Telegram workflows, and consumers can route them to separate channels without granting access to unrelated secrets. The remaining rollout and archival work is isolated in dedicated issues.
🤖 [rubykatzen/baseline]:
Goal
Move pull request and issue Telegram notifications into Baseline and export independent reusable workflows. PR notifications are a baseline repository capability; issue notifications are optional and may use a different Telegram channel.
Implemented
notify-telegram-pr-shared.ymlfor opened, reopened, ready, merged, and scheduled open-PR notifications.notify-telegram-issue-shared.ymlfor closed-issue notifications.TELEGRAM_BOT_TOKENandTELEGRAM_CHAT_IDexplicitly.Follow-ups
Result
Baseline now owns independent reusable PR and issue Telegram workflows, and consumers can route them to separate channels without granting access to unrelated secrets. The remaining rollout and archival work is isolated in dedicated issues.
🔔🧹✅