3c17b963f3
Forgejo Actions runner on the stage server picks up these jobs. Runs on the same labels `[self-hosted, linux]` — same self-hosted box as the Docker registry and the stage itself. deploy-stage is simplified: no SSH round-trip (runner and stage are the same host), just `cp` + `docker compose pull/up`. POS job kept as-is; it's gated on tag/dispatch and a Windows runner, so on Forgejo it'll simply not match any runner and stay queued — that's fine, POS ships from tags only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
19 lines
731 B
YAML
19 lines
731 B
YAML
name: Notify CI failures
|
|
|
|
on:
|
|
workflow_run:
|
|
workflows: ["CI", "Docker Images"]
|
|
types: [completed]
|
|
|
|
jobs:
|
|
telegram:
|
|
if: ${{ github.event.workflow_run.conclusion == 'failure' }}
|
|
runs-on: [self-hosted, linux]
|
|
steps:
|
|
- name: Ping Telegram
|
|
run: |
|
|
curl -sS -X POST "https://api.telegram.org/bot${{ secrets.TELEGRAM_BOT_TOKEN }}/sendMessage" \
|
|
--data-urlencode "chat_id=${{ secrets.TELEGRAM_CHAT_ID }}" \
|
|
--data-urlencode "text=CI FAILED: ${{ github.event.workflow_run.name }} on ${{ github.event.workflow_run.head_branch }} (${GITHUB_SHA:0:7}). https://github.com/${{ github.repository }}/actions/runs/${{ github.event.workflow_run.id }}" \
|
|
> /dev/null
|