Skip to content

Consolidate Telegram PR and issue notifications in Baseline #117

Description

@ineedjet

🤖 [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

  • 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.
  • Released the implementation in Baseline.

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.

🔔🧹✅

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions