gitea: Workflow YAML files are not executed on one Gitea instance

Description

Dear Gitea developers,

One (podman) Gitea instance runs on hostA and is configured with one action runner. The Gitea webpage shows that the runner is idle. Unfortunately, it does not execute any workflow YAML file when I push something into the repo. Actions are enabled for the repository and I see the registered and idle runner in the runner section of my project.

Here you see an example workflow YAML file:

$ cat .gitea/workflows/demo.yaml
name: Gitea Action Demo 1st
run-name: "foobar run-name"
on: [push]
jobs:
  Explore-Gitea-Actions:
    runs-on: mylinux
    steps:
      - run: echo "Hello world! G"

Here you see the runner config for hostA

$ cat .runner 
{
  "WARNING": "This file is automatically generated by act-runner. Do not edit it manually unless you know what you are doing. Removing this file will cause act runner to re-register as a new runner.",
  "id": 10,
  "uuid": "<hidden>",
  "name": "MyRunnerOne",
  "token": "<hidden>",
  "address": "https://hostA.domain.tld:9500",
  "labels": [
    "mylinux"
  ]
}

If I start the Gitea instance on a host B (and adjusting the host part of gitea/conf/app.ini), the workflow YAML file is executed.

Here you see

 $ cat .runner
{
  "WARNING": "This file is automatically generated by act-runner. Do not edit it manually unless you know what you are doing. Removing this file will cause act runner to re-register as a new runner.",
  "id": 5,
  "uuid": "<hidden>",
  "name": "MyRunnerTwo",
  "token": "<hidden>",
  "address": "https://hostB.domain.tld:9500",
  "labels": [
    "mylinux"
  ]
}

$ ./act_runner daemon -c my_host.yaml 
INFO[2023-07-18T10:52:15+02:00] log level changed to trace                   
INFO[2023-07-18T10:52:15+02:00] Starting runner daemon                       
DEBU[2023-07-18T10:52:15+02:00] gc: 2023-07-18 10:52:15.53170761 +0200 CEST m=+0.007769999  module=artifactcache
WARN[2023-07-18T10:52:15+02:00] Because the Gitea instance is an old version, skip declare labels and version. 

Here is the gitea log output when pushing a change to gitea/workflows/demo.yaml:

2023/07/18 10:56:35 ...eb/routing/logger.go:102:func1() [I] router: completed POST /api/actions/runner.v1.RunnerService/FetchTask for 10.0.2.100:34392, 200 OK in 45.5ms @ <autogenerated>:1(http.Handler.ServeHTTP-fm)
2023/07/18 10:56:35 ...eb/routing/logger.go:102:func1() [I] router: completed GET /my_repo/Sandbox_public.git/info/refs?service=git-receive-pack for 10.0.2.100:34408, 401 Unauthorized in 2.0ms @ repo/http.go:532(repo.GetInfoRefs)
2023/07/18 10:56:45 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/data/git/repositories/my_repo/sandbox_public.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= receive-pack --stateless-rpc --advertise-refs .
2023/07/18 10:56:45 ...eb/routing/logger.go:102:func1() [I] router: completed GET /my_repo/Sandbox_public.git/info/refs?service=git-receive-pack for 10.0.2.100:34408, 200 OK in 163.8ms @ repo/http.go:532(repo.GetInfoRefs)
2023/07/18 10:56:45 ...dules/git/command.go:281:Run() [D] git.Command.RunDir(/data/git/repositories/my_repo/sandbox_public.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= receive-pack --stateless-rpc /data/git/repositories/my_repo/sandbox_public.git
2023/07/18 10:56:45 ...eb/routing/logger.go:102:func1() [I] router: completed POST /myrepo/Sandbox_public.git/git-receive-pack for 10.0.2.100:34408, 200 OK in 202.8ms @ repo/http.go:500(repo.ServiceReceivePack)

Here is the server section of hostA in conf/app.ini

[server]
APP_DATA_PATH = /data/gitea
DOMAIN = hostA.domain.tld
SSH_DOMAIN = hostA.domain.tld
PROTOCOL = https
HTTP_PORT = 9500
ROOT_URL = https://hostA.domain.tld:9500/
LOCAL_ROOT_URL = https://hostA.domain.tld:9500/
CERT_FILE = pub.pem
KEY_FILE = key.pem
DISABLE_SSH = false
SSH_PORT = 22
SSH_LISTEN_PORT = 22
LFS_START_SERVER = true
LFS_JWT_SECRET = <hidden>
OFFLINE_MODE = true

Does anyone know what to do if a workflow YAML is ignored after a push action?

Gitea Version

1.20 and 1.19.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

git version 2.40.1

Operating System

podman with docker container image docker.io/gitea/gitea 1.20

How are you running Gitea?

podman with docker container image docker.io/gitea/gitea 1.20:

podman run --name my_gitea    \
    -e USER_UID=1000  \
    -e USER_GID=100 \
    -v /path/to/gitea_data:/data \
    -v /path/to/key.pem:/data/gitea/key.pem \
    -v /path/to/pub.pem:/data/gitea/pub.pem \
    -v /etc/localtime:/etc/localtime:ro \
    -p 9500:9500 \
    -p 2222:22 \
    gitea/gitea:1.20

Database

SQLite