You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
No response
Describe the solution you'd like
I would like the ability to manually provide the user that triggered the GH Actions workflow run.
Currently the person that created the API key is attributed to the workflow run. I can see in the code that the x-attribution-actor-id header is being set but according to this that only works on your internal tools. I mention that because I considered using curl to trigger the workflow runs.
Ideally would be an additional input that would provide us some flexibility on setting this value (possible for workflows to be triggered by bots) but would happy with it pulling the username from the github context.
What is the motivation / use case for changing the behavior?
Currently all the workflow runs that are triggered show as the person that generated the API key which is is confusing and doesn't look great for us when other teams use the tool.
The text was updated successfully, but these errors were encountered:
this would be very useful for us as well
my team members are using filters: "My Pipelines" in the circleci dashboard and it's missing the workflows triggered from GHA
Was coming here to investigate this as well, as we are trying to transition to GitHub Actions to support Merge Queues. This is one of two big subtractions of existing functionality with the direct integration (commit messages no longer showing up is the other).
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
No response
Describe the solution you'd like
I would like the ability to manually provide the user that triggered the GH Actions workflow run.
Currently the person that created the API key is attributed to the workflow run. I can see in the code that the x-attribution-actor-id header is being set but according to this that only works on your internal tools. I mention that because I considered using curl to trigger the workflow runs.
Teachability, documentation, adoption, migration strategy
Ideally would be an additional input that would provide us some flexibility on setting this value (possible for workflows to be triggered by bots) but would happy with it pulling the username from the github context.
What is the motivation / use case for changing the behavior?
Currently all the workflow runs that are triggered show as the person that generated the API key which is is confusing and doesn't look great for us when other teams use the tool.
The text was updated successfully, but these errors were encountered: