-
Notifications
You must be signed in to change notification settings - Fork 7
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
Is it possible to have the actions done as a bot? #212
Comments
@louim there is no default token available specifically for this action. That said, you should be able to use any GitHub authorization token that's valid for the actions that you mentioned. Also, you don't necessarily need to use a custom PAT,
|
@jonabc yeah, sorry I wasn't clear, I'm using a custom PAT to get around the reason you mention (default action token not re-triggering a run). |
Ah I see. Yeah unfortunately there's no common PAT or other authorization mechanism I'm aware of to bypass notifications when using a PAT on your account. I haven't kept close track of changes or updates to notifications and token usage though, maybe there's something in the help docs? If not, would creating a helper/bot type user account be an option and using PATs created on the other account to restrict or manage notifications? |
you can use https://github.com/actions/create-github-app-token. Just register an app that you want to be the actor with the permissions and access needed, then pass the token into this action and you should be golden |
Hey! Thanks for creating this action.
I was wondering if it's possible to have the actions (like the commits, branch and comments creation) done as non user? Is there a different token I could use for this?I'm currently using a PAT. I'm trying not to get pinged each time a branch/issue is created 😄
A bit more context, i'm currently using a different token like here https://github.com/github/licensed/blob/31b44067a069b7601060af337d7c27571486728f/.github/workflows/licensed.yml#L53.
The text was updated successfully, but these errors were encountered: