CI: PR standards workflow fails with invalid GraphQL field #4496

Closed
opened 2026-02-16 17:44:22 -05:00 by yindo · 2 comments
Owner

Originally created by @CasualDeveloper on GitHub (Jan 9, 2026).

Originally assigned to: @thdxr on GitHub.

Bug Description

The check-standards job fails for all PRs with:

Field 'issuesReferences' doesn't exist on type 'PullRequest'

Discovered when submitting #7443:
https://github.com/anomalyco/opencode/actions/runs/20845955619/job/59889485904?pr=7443

Root Cause

The GraphQL query uses issuesReferences, but the correct field name in GitHub's API is closingIssuesReferences.

Impact

All external contributor PRs fail the check-standards check.

Fix

Update the field name to closingIssuesReferences:

- issuesReferences(first: 1) {
+ closingIssuesReferences(first: 1) {
- const linkedIssues = result.repository.pullRequest.issuesReferences.totalCount;
+ const linkedIssues = result.repository.pullRequest.closingIssuesReferences.totalCount;

Reference

Originally created by @CasualDeveloper on GitHub (Jan 9, 2026). Originally assigned to: @thdxr on GitHub. ## Bug Description The `check-standards` job fails for all PRs with: ``` Field 'issuesReferences' doesn't exist on type 'PullRequest' ``` Discovered when submitting #7443: https://github.com/anomalyco/opencode/actions/runs/20845955619/job/59889485904?pr=7443 ## Root Cause The GraphQL query uses `issuesReferences`, but the correct field name in GitHub's API is `closingIssuesReferences`. ## Impact All external contributor PRs fail the `check-standards` check. ## Fix Update the field name to `closingIssuesReferences`: ```diff - issuesReferences(first: 1) { + closingIssuesReferences(first: 1) { ``` ```diff - const linkedIssues = result.repository.pullRequest.issuesReferences.totalCount; + const linkedIssues = result.repository.pullRequest.closingIssuesReferences.totalCount; ``` ## Reference - GitHub GraphQL API docs: https://docs.github.com/en/graphql/reference/objects#pullrequest
yindo closed this issue 2026-02-16 17:44:22 -05:00
Author
Owner

@CasualDeveloper commented on GitHub (Jan 9, 2026):

cc @rekram1-node - you wrote this workflow, was the change to issuesReferences intentional? The field doesn't seem to exist in GitHub's GraphQL schema. Happy to update the PR if there's a different field you were trying to use.

@CasualDeveloper commented on GitHub (Jan 9, 2026): cc @rekram1-node - you wrote this workflow, was the change to `issuesReferences` intentional? The field doesn't seem to exist in GitHub's GraphQL schema. Happy to update the PR if there's a different field you were trying to use.
Author
Owner

@CasualDeveloper commented on GitHub (Jan 9, 2026):

Already fixed by Aiden in 7c2907cbb ("ci: fix failing pipeline").

@CasualDeveloper commented on GitHub (Jan 9, 2026): Already fixed by Aiden in 7c2907cbb ("ci: fix failing pipeline").
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4496