From d06be3db013ee251adf2d8d9f98c0a5db5ffa0a3 Mon Sep 17 00:00:00 2001
From: ci-smoke <ci@tachoanal.com>
Date: Sun, 21 Jun 2026 18:38:48 +0200
Subject: [PATCH] smoke: prove the forgejo-runner executes a job

---
 .forgejo/workflows/smoke.yml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 .forgejo/workflows/smoke.yml

diff --git a/.forgejo/workflows/smoke.yml b/.forgejo/workflows/smoke.yml
new file mode 100644
index 0000000..84bd236
--- /dev/null
+++ b/.forgejo/workflows/smoke.yml
@@ -0,0 +1,16 @@
+# Smoke workflow pushed by smoke-runner.sh into a throwaway ci-smoke repo to
+# prove the forgejo-runner actually EXECUTES a job (not just "registered").
+# runs-on: docker -> the job runs as a CONFINED container INSIDE the isolated
+# dind daemon (the act image), which also exercises the dind + job-container path
+# the real CI uses. We deliberately do NOT use a `host` label (that would run the
+# step in the runner container, which holds the dind admin certs).
+name: smoke
+on: [push]
+jobs:
+  smoke:
+    runs-on: docker
+    steps:
+      - run: |
+          echo "forgejo-runner smoke OK (docker backend / dind)"
+          echo "container: $(uname -srm)"
+          echo "date: $(date -u +%FT%TZ)"