-
|
Hi, I cannot find any documentation on which PAT permissions to use for Is this supported and, if so, what permissions are required? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey! For organization-owned repositories, you'll typically need a Fine-grained PAT with (Read-only) and (Read-only) permissions for the specific repository. If you are using a Classic PAT, the scope is usually sufficient. One important thing to check is whether your organization has 'Fine-grained personal access tokens' enabled in their settings (under 'Personal access tokens' -> 'Settings'). If they require approval for PATs, your token won't work until an admin approves it. Also, ensure the organization hasn't restricted access to Copilot for certain tokens. |
Beta Was this translation helpful? Give feedback.
@pratikrath126
Thanks, but the PAT for user-owned repositories mentions the
Copilot Requestspermission, which is not available for organization-owned PATs. If you want to assign a PAT with read-only permissions for a specific organization-owned repository, the PAT needs to be owned by the organization.I went ahead and used a PAT owned by me with the permissions mentioned here. It works fine in a organization-owned repository.
Closing this discussion.