Skip to content
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

Request: Set the user that initiated the trigger #57

Open
1 task done
robbismith opened this issue Apr 27, 2023 · 2 comments
Open
1 task done

Request: Set the user that initiated the trigger #57

robbismith opened this issue Apr 27, 2023 · 2 comments

Comments

@robbismith
Copy link

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.

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.

@nimrodV81
Copy link

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

@prpetten
Copy link

prpetten commented Feb 6, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants