zweiter "Actions" Versuch

.forgejo/workflows/demo.yaml

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

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

@@ -0,0 +1,23 @@
+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: alpine
+    commands:
+      - ls ~
+      - pwd
+      - ls -la /
+      - touch /was-duerfen-wir
+      - who
+      - uname -a
+      - id
+      - groups
+      - last
+  - name: going-private
+    image: debian
+    commands:
+      - eval $MYTEST_MYCMD #sind geschachtelte Secrets möglich?
+    secrets: [ SECRET_API_TOKEN, mytest_mycmd ]

Technisches/actions-einrichten.md

@@ -15,3 +15,11 @@
         - 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