[GitHub connector] Ready-for-review operation queries invalid Repository.fullDatabaseId

What issue are you seeing?

In ChatGPT Work, the official GitHub connector cannot mark a draft pull request as Ready for review.

The connector operation github.mark_pull_request_ready_for_review fails with:

GithubGraphQLAPIError: Field 'fullDatabaseId' doesn't exist on type 'Repository'
Path: mutation.markPullRequestReadyForReview.pullRequest.headRepository.fullDatabaseId

The problem was reproduced twice on 28 August 2026 against an open draft pull request in a private repository.

An independent pull-request read after each attempt still reported draft: true, confirming that GitHub rejected the GraphQL document before executing the mutation.

Using GitHub’s normal Ready for review button manually succeeded immediately. Other GitHub connector reads and subsequent pull-request operations continued to work.

This appears to be a field-selection bug in the connector’s normalized response query, rather than a GitHub outage, repository-specific issue, or authentication failure.

What steps can reproduce the bug?

1. Connect the official GitHub connector to ChatGPT Work.
2. Create or select an open draft pull request.
3. Ask ChatGPT Work to mark the pull request Ready for review.
4. Allow it to invoke github.mark_pull_request_ready_for_review.
5. Observe the GraphQL schema error referencing:
   markPullRequestReadyForReview.pullRequest.headRepository.fullDatabaseId
6. Independently read the pull request.
7. Observe that it remains a draft.

The failure was reproduced twice before the pull request was manually marked Ready through GitHub’s interface.

What is the expected behavior?

The connector should execute markPullRequestReadyForReview successfully and return its normalized pull-request snapshot without requesting fields that do not exist on their GraphQL object types.

An independent pull-request read should then report draft: false.

Additional information

GitHub’s official schema changelog records fullDatabaseId being added to PullRequest, PullRequestReview, and PullRequestReviewComment on 9 February 2024. It does not record that field being added to Repository:

https://docs.github.com/en/graphql/overview/changelog/2024#schema-changes-for-2024-02-09

The most likely cause is that the connector applies a pull-request response field set containing fullDatabaseId to the nested headRepository object.

GitHub validates the complete GraphQL document before executing the mutation, so this invalid nested selection prevents the Ready transition entirely.

The connector’s general update_pull_request operation does not expose a draft/ready parameter, so there is no alternative connector action available.

The installed connector metadata reports contains_mcp_source: false; only its operation schema is locally available. The faulty GraphQL implementation cannot be patched by the user.

Start by tracing the github.mark_pull_request_ready_for_review operation and its normalized response selection for markPullRequestReadyForReview.pullRequest.headRepository. Verify where Repository.fullDatabaseId is requested, then compare that selection with GitHub’s schema changelog. Done means the mutation validates, the pull request becomes ready for review, and an independent read reports draft: false.