`Personal access tokens with fine grained access do not support the GraphQL API`
with a PAT that has both repo and project scopes, I'm getting the following when trying to use the action:
Personal access tokens with fine grained access do not support the GraphQL API
Let me know if there's any troubleshooting I can do on my end; also, I'm wondering if this is a known issue?
@aaronArinder only classic PATs currently are supported by the api that drives this action. Use a classic PAT instead of a fine grained one
FWIW this was fixed in https://github.com/github/roadmap/issues/622, the docs should probably be updated.
What permissions are needed for the fine grained token?
Fine grained tokens work provided the token has the following:
- Repositories
- Issues: Read
- Metadata: Read
- Organization
- Projects: Read and Write
Fine grained tokens work
You forgot about the non-negligible caveat that so far, project permissions are only available to organization accounts.
There is no such option when the "resource owner" of a fine-grained token is a regular user.
Correct 👍 - I'm using this action with fine-grained tokens as described in https://github.com/actions/add-to-project/issues/289#issuecomment-1839684489 with a GitHub organization.
👋🏻 It's correct that fine-grained tokens are supported for organization owned projects, and our documentation has been updated to reflect that. It's true that user-owned projects are not accessible with PATv2 at the moment, but this is on our product roadmap.