image auf codeberg ist erreichbar und nun?

versuche simples Secret als TestCommand

.forgejo/workflows/demo.yaml

@@ -0,0 +1,6 @@
+on: [push]
+jobs:
+  test:
+    runs-on: docker
+    steps:
+      - run: echo All God (ein kleiner Scherz ;-)

.woodpecker/ist-image-erreichbar.yaml

@@ -0,0 +1,12 @@
+when:
+  - event: push
+    branch: [no-real-branch, feature/working-*]
+    #https://woodpecker-ci.org/docs/usage/workflow-syntax#when---conditional-execution
+
+steps:
+  - name: wie-weit-komme-ich-im-image_resp_plugin
+    image: codeberg.org/xfix/plugin-codeberg-pages-deploy:1
+    settings:
+      folder: Blog
+      ssh_key:
+        from_secret: clioption

.woodpecker/woodpecker-workflow-adavanced-test.yaml

@@ -0,0 +1,25 @@
+when:
+  - event: push
+    branch: [no-real-branch, feature/working-*]
+    #https://woodpecker-ci.org/docs/usage/workflow-syntax#when---conditional-execution
+
+steps:
+  - name: wir-testen-die-umgebung
+    image: debian
+    commands:
+      - ls ~
+      - pwd
+      - ls -la /
+      - touch /was-duerfen-wir
+      - who
+      - uname -a
+      - id
+      - groups
+      #- sudo last ## im alpine image gegenchecken, was dort verfügbar
+      #- sudo ls /var
+      - last
+## secrets existieren nur in images / "plugin"s / build-steps
+  - name: image-test
+    image: codeberg.org/xfix/plugin-codeberg-pages-deploy
+    commands:
+      - docker images

.woodpecker/woodpecker-workflow-test.yaml

@@ -0,0 +1,20 @@
+# https://woodpecker-ci.org/docs/usage/intro
+when:
+  - event: push
+    branch: feature/working-forgejo-actions
+#gehen wildcards fuer branch filtering?
+
+steps:
+  - name: build
+    #image: debian # alpine // docker pull docker.io/library/alpine
+    image: ubuntu:22.04
+    commands:
+      - echo "This is the build step"
+      #wie kann man Bash Shebang nutzen?
+      - echo "echo Woodoo Woodoopecker" > executable
+      #chmod u+x executable 
+  - name: a-test-step
+    image: alpine #golang:1.16
+    commands:
+      - echo "Testing ..."
+      - /bin/sh ./executable

Technisches/actions-einrichten.md

@@ -0,0 +1,25 @@
+# Actions unter [Woodpecker](https://woody.git.rpi-virtuell.de/) einrichten
+
+## workflows, runner, ...
+
+- [Forgejo Actions user guide](https://forgejo.org/docs/next/user/actions/)
+    - Actions aktivieren (pro Repo)
+        - Settings => Repo Units => Overview => "Enable integrated CI... with.. Actions"
+    - in .forgejo/workflows YAML Dateien, die Action "definieren" - ähnlich [GitHub Actions](https://docs.github.com/en/actions)
+        - .forgejo/workflows/demo.yaml
+    - wo/wie/was ist der "runner"???
+
+- Workflow in Woodpecker
+    - [Getting Started](https://woodpecker-ci.org/docs/usage/intro)
+        - "enable" Repo
+        - Workflow als YAML in Verzeichnis .woodpecker
+        - Bsp.: .woodpecker/woodpecker-workflow-test.yaml
+
+- Vermutung
+    - Actions in Woodpecker sind vgl. mit "danger zone" in Forgejo, haben nichts gemein!!!
+    - Actions in Forgejo ~~== Workflow in Woodpecker
+    - Actions in Forgejo sind Instanzen für "forgejo runner"
+    - Woodpecker ist davon unabhängig
+    - Actions können deaktiviert werden
+    - https://forgejo.org/docs/latest/admin/actions/: "Forgejo Actions provides continuous integration driven from the files found in the .forgejo/workflows directory of a repository. Note that Forgejo does not run the jobs, it relies on the Forgejo runner to do so. It needs to be installed separately."
+    - ~~[Forgejo Actions user guide](https://forgejo.org/docs/next/user/actions/)~~ irrelevant