erster "Actions" Versuch

.woodpecker/woodpecker-workflow-test.yaml

@@ -0,0 +1,24 @@
+#
+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"
+      - cat << EOF > simple-shell-test.sh
+#!/bin/bash
+echo 'ich bin keine Katze'
+cat 'und auch kein Hund'
+ls -la /
+EOF
+#chmod u+x executable 
+  - name: a-test-step
+    image: alpine #golang:1.16
+    commands:
+      - echo "Testing ..."
+      - ./executable

Technisches/actions-einrichten.md

@@ -0,0 +1,17 @@
+# 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
+