Reusable Forgejo Actions for Hydra-hosted projects

Find a file

dprevatt 90b537877b rename: drop Hydra prefix, refer to CI notification hub		2026-05-31 16:12:01 +00:00
notify	Initial: notify composite action posting to Hydra n8n hub	2026-05-25 22:50:43 -05:00
README.md	rename: drop Hydra prefix, refer to CI notification hub	2026-05-31 16:12:01 +00:00

README.md

ci-actions

Reusable Forgejo Actions (compatible with GitHub Actions) for projects hosted on git.prevatt.cloud.

`notify` — CI event notifications

Posts a job-status event to the CI notification hub (n8n workflow CI Notify), which routes to ntfy with appropriate priority and tags. Future evolution will fan out to per-app Slack channels and Home Assistant → Alexa announcements without any workflow changes.

Usage

Add as the last step in any job that you want notifications for:

- name: Notify
  if: always()
  uses: dprevatt/ci-actions/notify@main
  with:
    status: ${{ job.status }}
    title: "Fixins build"

How routing works

`status`	ntfy topic	ntfy priority	tags	Future destinations
`success`	`ci`	2 (low)	`white_check_mark,ci`	#ci- on Slack
`failure`	`alerts`	5 (max)	`warning,ci,build`	HA → Alexa announcement; #ci- on Slack
`cancelled`	`ci`	2 (low)	`x,ci`	#ci- on Slack

The priority + topic split is what makes the difference between "annoy me on my phone immediately" (failures) and "let me check the history later if I care" (everything else).

Why a webhook hub and not direct ntfy?

So that the notification policy (priorities, topics, fan-out targets) lives in one place — the n8n workflow — and individual projects don't need to know about it. Add a Slack node in n8n and every project that already uses this action gets Slack notifications automatically. No workflow file changes.

Failure isolation

If the n8n hub is down, this action logs a warning but does NOT fail the job. Your build's exit status is independent of whether the notification went through.

Future actions

Things likely to land here as Hydra grows:

setup-bws — fetch a secret from Bitwarden Secrets Manager at runtime
setup-buildkit-podman — configure buildx with the Podman socket for Forgejo Actions runners in LXCs
notify-deploy — same hub, different semantics: deploy succeeded / rolled back / etc.