-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include triggering_actor in GitHub Workflow Runs #314
Comments
If you do some comparative testing, is the I can see we don't include either at the current moment in time, however based on the SDK we're using to obtain the data, they don't seemingly have a concept of |
I believe that, for my specific use-case, According to this post on when GitHub introduced the differentiation, a workflow will have a That is:
In this case, |
Did some investigation, have now requested the relevant data be included in the |
Thanks. Looking forward to this change (except I think you mean |
Yeah I did 😂 - sorry, I'm looking at things in both libraries now and I keep cross typing the names. |
SDK v54.0.0 contains the new field on struct - assuming no other breaking changes we should now be able to action this request. |
Is your feature request related to a problem? Please describe.
We have a few workflows internally we'd like to aggregate metrics on. One of them is "who is the person who mostly triggers it per week?".
Describe the solution you'd like
The GitHub API for workflow runs includes
triggering_actor
as a field, and so does the GitHub Actions workflows UI.Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: