Forgejo Actions
Forgejo Actions is developed by the Forgejo team. It allows GitHub-actions based workflows and is directly integrated into Forgejo, the software powering CodeFloe.
Available Runners
Section titled “Available Runners”To run an action, you need to delegate it to an available runner.
All runner have labels set which can be referenced in the runs-on field.
All available labels are listed at https://codefloe.com/user/settings/actions/runners (Login required).
Some labels reference multiple runners while others reference a single runner.
The names aim to describe the underlying environment in a descriptive manner.
Example Workflow
Section titled “Example Workflow”An example workflow could look like this:
name: hello-world
on:
push:
workflow_dispatch:
jobs:
hello-world:
runs-on: debian-latest
defaults:
run:
shell: sh
steps:
- name: hello-world
run: |
echo "Hello, World!"
sleep 30Platform Support
Section titled “Platform Support”Custom Containers
Section titled “Custom Containers”All jobs run within containers.
The runs-on: key specifies a compatible NodeJS image (either LTS or latest) which is able to execute Actions.
You can also use the containers: key to specify an arbitrary container image for a job of yours.
Note that when doing so, Actions are not supported if this image does not have NodeJS installed.
name: hello-world
on:
push:
workflow_dispatch:
jobs:
hello-world:
runs-on: debian-latest
container:
image: library/alpine:latest
defaults:
run:
shell: sh
steps:
- name: hello-world
run: |
echo "Hello, World!"
sleep 30Support
Section titled “Support”If you encounter usage issues and/or have feature requests regarding Actions itself, please report them directly in the respective Forgejo repository. If you instead face any issues using Actions on CodeFloe, you are welcome to open a thread in our Forum.