Gitea Actions Print gitea.actor Value Which Are Different from GitHub Action in Special Circumstances

[dangjinghao]

Description

when a cron workflow is triggered, the {{ gitea.actor }} whould be replaced with gitea-actions but github action would print the username who set the trigger.

Gitea Version

1.22.6

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

workflow configuration

name: cron
on:
  schedule:
    - cron: "*/2 * * * *"
env:
  TZ: Asia/Shanghai

jobs:
  echo:
    runs-on: ubuntu-latest
    steps:
    - name: test
      run: |
        echo ${{ github.actor }}        

gitea:1.22.6, running in docker container, image: gitea/gitea:latest
gitea-runner version: v0.2.11, running in docker container, image: gitea/act_runner:latest

Database

None

[Zettat123]

In fact, this is by design. The reason is that in some cases Gitea cannot get the actor when creating schedule tasks (see #30581).

I checked the GitHub documentation and found that GitHub may require users to alter the cron to reactivate the scheduled workflow. Indeed, the actor can always be recorded in this way. But I'm not sure if we should do this as it requires users to do more operations to activate/reactivate the workflow.