-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Possible to use Github Apps tokens instead of PAT? #68
Comments
Hi @alfieyfc I haven't tested it, but I see no reason why it wouldn't work provided the GitHub Apps tokens have the correct scopes. I would guess that it didn't work because the other conditions weren't met. Just in case, check your token has the correct scopes. I think it should be similar to this setup: https://github.com/peter-evans/create-pull-request/blob/master/docs/concepts-guidelines.md#authenticating-with-github-app-generated-tokens |
It doesn't work for this similar repo either, fyi |
Good to know, thanks. To clarify, I think what is unexpected is that it doesn't work with GitHub App tokens. That should work because they are very similar to a PAT in the sense that you can define what scopes it has. I will make a request to GitHub support to ask them about it. |
GitHub Support have confirmed our findings, that it works with a PAT but not with GitHub App tokens. An internal issue has been raised with the engineering team to determine if this behaviour is expected. |
Do they have a plan to add the necessary scopes to GITHUB_TOKEN, or this scopes will open security holes? |
I can't speak for GitHub, but I'm fairly confident that these scopes will not be added to the default |
I know in the docs it says that it's required a repo scoped Personal Access Token (PAT) is used, where
GITHUB_TOKEN
won't work.Is it possible to use Github Apps instead of PAT, which seems more appropriate in organization projects?
I tried something like this and doesn't work, even with all permissions set to
Read & Write
for the App.Error message isn't very informative:
The text was updated successfully, but these errors were encountered: