dprevatt/forgejo-template-app
Template
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Starter template wired into the Hydra CI Notify hub
6 commits 1 branch 0 tags 37 KiB
Find a file Use this template
Exact
dprevatt 646c44eb63
All checks were successful
CI / verify (push) Successful in 16s
Details
rename: drop Hydra prefix in step name
2026-05-31 16:12:05 +00:00
.forgejo/workflows rename: drop Hydra prefix in step name 2026-05-31 16:12:05 +00:00
.gitignore Initial template: CI workflow with Hydra notify step 2026-05-27 23:53:37 -05:00
README.md rename: drop Hydra prefix 2026-05-31 16:12:03 +00:00

README.md

forgejo-template-app

Starter template for new repos hosted on git.prevatt.cloud. Every project created from this template is wired into the CI Notify hub on day one — no copy-paste from another repo, no forgotten webhook.

What's in the box

  • .forgejo/workflows/ci.yml — a starter CI workflow with a placeholder verify job and a Notify CI hub step that posts every run's outcome to https://n8n.prevatt.cloud/webhook/hydra-ci-notify.

The hub workflow (CI Notify in n8n, id XWWhVmJqqKpBr92Q):

  1. Sends a push notification via ntfy (topic ci on success/cancel, alerts on failure).
  2. Creates a Slack channel ci-<repo-name> if one doesn't exist.
  3. Auto-invites the primary user to the channel on first creation.
  4. Posts a formatted status message to the channel.

How to use this template

  1. Create a new repo on git.prevatt.cloud and pick this repo as the template (toggle "Make Repository a Template" must be on here — already set).
  2. Open .forgejo/workflows/ci.yml and replace the Placeholder step with your real build / test / lint steps. Leave the Notify step at the end of the job; the if: always() clause is what reports failures.
  3. Push — the first run will create the per-repo Slack channel and invite you.

Adding build & publish

If the project ships container images, copy the build-and-push job from dprevatt/Fixins (.forgejo/workflows/build-and-publish.yml). It already handles the buildx-driver and PACKAGES_TOKEN quirks specific to the Forgejo Actions + Podman runner setup.

Why a fully-qualified uses: URL

Forgejo's DEFAULT_ACTIONS_URL on this instance is set to github, which resolves bare uses: org/repo@ref against github.com (so things like actions/checkout@v4 keep working as expected). To reference an action that lives on git.prevatt.cloud, write the full URL:

uses: https://git.prevatt.cloud/dprevatt/ci-actions/notify@main

This was validated end-to-end against Forgejo 15.0.2 / act_runner 12.10.1.