Remove invalid IssueField fragment from set_issue_field discovery query

[Copilot]

set_issue_field field discovery was failing at GraphQL validation because the query referenced ... on IssueField, a type that is not present in the current GitHub schema. This prevented field resolution from completing before mutation execution.

• Query compatibility fix

  • Removed ... on IssueField { id name } from repository-level and organization-level issueFields selections in actions/setup/js/set_issue_field.cjs.
  • Kept only concrete field fragments (IssueFieldText, IssueFieldNumber, IssueFieldDate, IssueFieldSingleSelect, IssueFieldMultiSelect) so discovery remains schema-valid.

• Regression coverage

  • Updated set_issue_field.test.cjs assertions to ensure the query does not include the invalid IssueField fragment condition.
  • Added set_issue_field_api_query.integration.test.cjs to validate query execution against the live GraphQL schema. The test is wired into vitest.integration.config.mjs so it runs under the existing test:js-integration-live-api command and the js-integration-live-api CI job.

nodes {
  __typename
  ... on IssueFieldText { id name }
  ... on IssueFieldNumber { id name }
  ... on IssueFieldDate { id name }
  ... on IssueFieldSingleSelect { id name options { id name } }
  ... on IssueFieldMultiSelect { id name options { id name } }
}

[Copilot]

⚠️ Not ready to approve

The new live-API integration test is currently brittle/mis-scoped for CI execution, and an unrelated generated workflow lockfile change should be dropped unless intentional.

Pull request overview

Fixes set_issue_field GraphQL field-discovery by removing an invalid ... on IssueField fragment that fails schema validation, keeping discovery queries limited to concrete issue field types.

Changes:

• Removed the invalid ... on IssueField { id name } fragment from repo/org issueFields discovery selections.
• Updated the unit test to assert the query does not include the non-existent IssueField fragment.
• Added a new integration test file intended to validate the discovery query against the live GitHub GraphQL API schema/query execution.

File summaries

File	Description
actions/setup/js/set_issue_field.cjs	Removes the invalid IssueField fragment from the discovery query.
actions/setup/js/set_issue_field.test.cjs	Updates query-shape assertions to ensure the invalid fragment is absent.
actions/setup/js/set_issue_field_api_query.integration.test.cjs	Adds a live-API integration test for query validity and fragment exclusion.
.github/workflows/objective-impact-report.lock.yml	Updates generated workflow metadata hash (appears unrelated to this PR’s purpose).

Copilot's findings

• Files reviewed: 4/4 changed files
• Comments generated: 3

Note

Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[pelikhan]

@copilot run pr-finisher skill

[Copilot]

@copilot run pr-finisher skill

Done in 4e8fbb7:

• Dropped the unrelated lockfile change (objective-impact-report.lock.yml reverted)
• Removed the brittle __type(name: "IssueField") == null introspection assertion — the integration test now simply executes the discovery query and asserts the response is defined, which is the schema-validity check that matters
• Wired the integration test into vitest.integration.config.mjs so it runs under the existing test:js-integration-live-api command and the js-integration-live-api CI job