Update .gitea/workflows/fedora-checkout.yml

update runner name

.gitea/workflows/fedora-checkout.yml

@@ -1,13 +1,14 @@
-name: release
+name: checkout
 
-on: 
+on:
   push:
-    tags:
-      - '*'
+    branches:
+      - main  # Or your desired branch
 
 jobs:
-  release:
-    runs-on: ubuntu-latest
+  checkout:
+    runs-on: fedora-latest
+
     steps:
       - uses: https://git.phyllo.me/actions/checkout@v4
         with:
@@ -16,4 +17,5 @@ jobs:
         with:
           files: |-
             bin/**
-          api_key: '${{secrets.RELEASE_TOKEN}}'
+          api_key: '${{secrets.RELEASE_TOKEN}}'
+

README.md

@@ -6,15 +6,45 @@ Gitea Actions closely resemble GitHub Actions, to the point that several GitHub
 
 ## How to test actions locally
 
-Download the latest version of the act runner for your architecture [here](https://dl.gitea.com/act_runner/)
+- Clone this repository locally
 
-Execute the act runner using the `exec` argument and specify the workflow file:
+- Download the latest version of the act runner for your architecture [here](https://dl.gitea.com/act_runner/)
+    - For instance, if your computer is running Linux with an amd64 processor: `act_runner-0.2.12-linux-amd64`
 
 ```
-./act_runner exec --workflows checkout.yml 
+curl https://dl.gitea.com/act_runner/0.2.12/act_runner-0.2.12-linux-amd64 --output act_runner
+```
+```
+  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+                                 Dload  Upload   Total   Spent    Left  Speed
+100 19.2M  100 19.2M    0     0   102M      0 --:--:-- --:--:-- --:--:--  103M
 ```
 
-## How they are used in Phyllome OS
+- Add execute permission
+
+```
+chmod +x act_runner 
+```
+
+- Run the act runner using the `exec` argument and specify the workflow file to be used:
+
+```
+./act_runner exec --workflows workflows/checkout.yml 
+```
+```
+INFO[0000] Using the only detected workflow event: push 
+INFO[0000] Planning jobs for event: push                
+INFO[0000] cache handler listens on: http://192.168.122.175:38917 
+INFO[0000] Start server on http://192.168.122.175:34567 
+[...]
+[checkout/checkout] ⭐ Run Main https://git.phyllo.me/actions/checkout@v4
+[checkout/checkout]   🐳  docker cp src=/home/lukas/test-actions/. dst=/home/lukas/test-actions
+[checkout/checkout]   ✅  Success - Main https://git.phyllo.me/actions/checkout@v4
+[checkout/checkout] Cleaning up container for job checkout
+[checkout/checkout] Cleaning up network for job checkout, and network name is: GITEA-ACTIONS-TASK-push_WORKFLOW-checkout_JOB-checkout-checkout-network
+```
+
+## How workflows are used in Phyllome OS
 
 Several known actions repositories are mirrored within Phyllome's Gitea instance, under the [actions](https://git.phyllo.me/actions) organization.
 

workflows/docker-in-docker.yml

@@ -0,0 +1,16 @@
+name: checkout
+
+on: 
+  push:
+    tags:
+      - '*'
+
+jobs:
+  checkout:
+    runs-on: ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest
+    container:
+      image: git.phyllo.me/roots/fedora-iso-creation:42
+    steps:
+    - uses: https://git.phyllo.me/actions/checkout@v4
+    - name: Setup tmate session
+    - uses: https://github.com/mxschmitt/action-tmate@v3

workflows/fedora-checkout.yml

@@ -0,0 +1,16 @@
+
+name: checkout
+
+on:
+  push:
+    branches:
+      - main  # Or your desired branch
+
+jobs:
+  checkout:
+    runs-on: fedora-latest
+
+    steps:
+      - uses: https://git.phyllo.me/actions/checkout@v4
+        with:
+          fetch-depth: 0

workflows/list-files-and-path.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   echo-path:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest
     steps:
       - uses: https://git.phyllo.me/actions/checkout@v4
         with:

workflows/release-tag.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   release:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest
     steps:
       - uses: https://git.phyllo.me/actions/checkout@v4
         with:
@@ -16,4 +16,6 @@ jobs:
         with:
           files: |-
             bin/**
-          api_key: '${{secrets.RELEASE_TOKEN}}'
+          api_key: '${{secrets.RELEASE_TOKEN}}'
+
+