Who will be the GitHub actor when a workflow runs on a schedule? #25067
-
|
The documentation at https://help.github.com/en/actions/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions#github-context states that github.actor resolves to The login of the user that initiated the workflow run. Now, who would that be when the workflow runs on a schedule? I noticed in https://github.com/ergebnis/composer-normalize/runs/388922221 (a scheduled run) that the actor resolves to localheinz (that’s me). |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
The latest user who create the schedule trigger will be the actor for the schedule workflow. As mentioned, you can export ‘github.actor’ in context for check. For instance, if user A create the schedule trigger, workflow is triggered with actor ‘user A’, then user B modified the schedule setting, workflow is triggered with actor ‘user B’. |
Beta Was this translation helpful? Give feedback.
-
|
So "git blame" for our workflow currently reads and User A shows up as the actor in the UI, like this: Or is the user in the UI not the actor? It seems that whoever added the |
Beta Was this translation helpful? Give feedback.
-
|
Just ran a bunch of tests of this. The user in the blame is not guaranteed to be the same as the actor; it just usually happens to be the same by coincidence. The real answer is this: the identity of the In other words, it has absolutely nothing to do with the In fact, GitHub fundamentally cannot use the By contrast, workflows are - I assume - entities that exist somewhere in a GitHub database which can only be updated by authorized operations. Using the principal of the authorization claim on the most recent update as the Here's a test I ran of this, where the commit that updated the workflow file was created with the email address of
|
Beta Was this translation helpful? Give feedback.
-
|
I think this answer is wrong. In my experience, it has nothing to do with who edited the |
Beta Was this translation helpful? Give feedback.
-
|
I asked GitHub support about this and got the following answer:
I had first tried to change the actor by merging a PR by the desired new user to the cron job .yml action. That did not change the actor. What did work was to log in as the new user and then disable and re-enable the workflow, as linked to above. |
Beta Was this translation helpful? Give feedback.
-
|
This is very inconvenient when it comes to sending workflow run notifications to a specific user. Are there any plans for an explicit "actor" option for scheduled workflows? |
Beta Was this translation helpful? Give feedback.
-
|
I think so. It’s uncomfortable because it’s not intuitive. |
Beta Was this translation helpful? Give feedback.
The latest user who create the schedule trigger will be the actor for the schedule workflow.
As mentioned, you can export ‘github.actor’ in context for check.
For instance, if user A create the schedule trigger, workflow is triggered with actor ‘user A’, then user B modified the schedule setting, workflow is triggered with actor ‘user B’.