forgejo-actions/README.md
RMSTechStudio 18e3769c76 docs: use full URL form in usage example
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-29 15:42:09 +02:00

1.5 KiB

forgejo-actions

Composite actions reused across all RMS Tech Studio repos.

notify-telegram

Pings a Telegram chat about a workflow outcome. Skips silently if credentials are missing.

Setup once (org-level) — in Forgejo, go to your org → Settings → Actions → Secrets, add:

  • TELEGRAM_BOT_TOKEN
  • TELEGRAM_CHAT_ID

These propagate to all repos under the org.

Usage in a workflow:

- name: Notify Telegram (success)
  if: success()
  uses: https://git.rmstechstudio.com/rmstechstudio/forgejo-actions/notify-telegram@main
  with:
    bot-token: ${{ secrets.TELEGRAM_BOT_TOKEN }}
    chat-id: ${{ secrets.TELEGRAM_CHAT_ID }}
    status: success
    title: "RMS Ecosystem deploy"
    message: ${{ github.event.head_commit.message }}

- name: Notify Telegram (failure)
  if: failure()
  uses: https://git.rmstechstudio.com/rmstechstudio/forgejo-actions/notify-telegram@main
  with:
    bot-token: ${{ secrets.TELEGRAM_BOT_TOKEN }}
    chat-id: ${{ secrets.TELEGRAM_CHAT_ID }}
    status: failure
    title: "RMS Ecosystem deploy"

Inputs:

Name Required Default Description
bot-token yes Telegram bot token
chat-id yes Telegram chat id
status yes success or failure
title yes Short label, e.g. "RMS Ecosystem deploy"
message no "" Extra body (commit msg, error summary…)
notify-on-success no true Set false for silent crons