Skip to content

fix: batches now supports fine-grained pat #1247

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

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions docs/admin/code_hosts/github.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -261,15 +261,11 @@ Fine-grained tokens can access public repositories, but can only access the priv

When creating your fine-grained access token, select the following permissions depending on the purpose of the token:

| Feature | Required token permissions |
| Feature | Required token permissions |
| ----------------------------------------------------- | ------------------------------------------------------ |
| [Sync private repositories](#private-repositories) | `Repository permissions: Contents - Access: Read-only` |
| [Sync repository permissions][permissions] | `Repository permissions: Contents - Access: Read-only` |
| [Batch changes][batch-changes] | `Unsupported` |



> WARNING: Fine-grained tokens don't support the `repositoryQuery` code host connection option or batch changes. Both of these features rely on GitHub's GraphQL API, which is [unsupported by fine-grained access tokens](https://docs.github.com/en/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql).
| [Batch changes][batch-changes] | `Repository permissions: Contents: Read and write, Metadata: Read-only, Pull requests: Read and write, Workflows: Read and write` |

### Private repositories

Expand Down