I’m maintaining an action that creates branches from issues.
A common usage pattern is that multiple developers in a single repository interact with this action (for example giving it ChatOps commands in issue comments).
However, all activities from the action are done under the
github-actions [bot] account.
I’m aware of the option to inject a Personal Access Token (PAT) into the action but this would make all the activities originate from the account that belongs to the PAT.
Any other options that I missed? If not, would it be a viable roadmap issue to have actions assume the user account that interacts with it?
Rob van der Leek