GitHub integration: Draft/Ready mutations fail because connector automatically queries nonexistent Repository.fullDatabaseId, blocking automated PR workflows

What issue are you seeing?

Description

The GitHub integration currently fails when changing a pull request between Draft and Ready for Review.

The connector automatically includes Repository.fullDatabaseId in the GraphQL response selection for these operations. That field is not present in GitHub's current GraphQL schema, causing the request to fail before the Draft/Ready transition can be completed.

This query is generated internally by the integration and is not user-configurable, so there is no way to work around the failure within the automated workflow. A user must manually open GitHub and change the pull request state before automation can continue.

Error

GithubGraphQLAPIError:
Field 'fullDatabaseId' doesn't exist on type 'Repository'

The error path for marking a PR Ready includes:

mutation
→ markPullRequestReadyForReview
→ pullRequest
→ headRepository
→ fullDatabaseId

I also observed the same Repository.fullDatabaseId schema error with the convertPullRequestToDraft mutation.

What steps can reproduce the bug?

Steps to reproduce
Connect GitHub to Codex/ChatGPT.
Open or use an existing Draft pull request.
Ask the GitHub integration to mark the PR as Ready for Review.
The operation fails with the GraphQL schema error above.

The failure was reproducible across multiple attempts, including delayed retries.

What is the expected behavior?

Expected behavior

The pull request should be transitioned from Draft to Ready for Review.

Actual behavior

The mutation fails because the connector's GraphQL response selection requests the nonexistent Repository.fullDatabaseId field.

Additional information

Additional information

Manually changing the PR to Ready for Review in the GitHub UI works normally. Subsequent GitHub Actions workflows also run normally. This suggests the repository and pull request state are valid and the failure is specific to the integration's GraphQL mutation/response handling.

This behavior had not occurred previously with the same GitHub workflow.

No source file is named. Start by locating the GitHub GraphQL handling for markPullRequestReadyForReview and convertPullRequestToDraft, then trace the generated Repository selection containing fullDatabaseId. Done means both mutations no longer request that schema field and successfully transition pull requests between Draft and Ready for Review.