GitHub GraphQL issue mutations accept assignee update inputs
Introduced 2026-07-14 · score 0.93
HOW TO USE IT
When a repository workflow updates issue assignees through GitHub GraphQL, use the `assignees` input field where applicable. Supply each assignee’s required `actorId` and any needed optional metadata.
mutation { addAssigneesToAssignable(input: { assignableId: "<ASSIGNABLE_ID>", assignees: [{ actorId: "<ACTOR_ID>", confidence: HIGH, rationale: "<REASON>", suggest: false }] }) { assignable { id } } }WHY THIS HELPS
When maintaining a repository workflow that updates issue assignees through GitHub GraphQL, use the new assignee input fields where applicable.
REQUIREMENTS AND LIMITATIONS
- AddAssigneesToAssignableInput.assignableId (required): ID of the assignable object to add assignees to.
- AddAssigneesToAssignableInput.assignees: Array of `AssigneeUpdateInput` actors to add; mutually exclusive with `assigneeIds`.
- AssigneeUpdateInput.actorId (required): ID of the user or bot to assign.
- AssigneeUpdateInput.confidence: Agent’s confidence level; allowed values are `HIGH`, `MEDIUM`, and `LOW`.
- AssigneeUpdateInput.rationale: Reason for selecting the assignee; maximum 280 characters.
- AssigneeUpdateInput.suggest: If true, stores the value as a pending suggestion for human review instead of applying it directly.
- ReplaceActorsForAssignableInput.assignees: Array of `AssigneeUpdateInput` actors to set as assignees; mutually exclusive with `actorIds` and `actorLogins`.
- UpdateIssueInput.assignees: Array of `AssigneeUpdateInput` actors to assign to the issue; mutually exclusive with `assigneeIds`.
FIRST-PARTY EVIDENCE
- https://docs.github.com/en/graphql/overview/changelog#schema-changes-for-2026-07-14
- https://docs.github.com/en/graphql/reference/issues
Check the installed version and the source before using it. Entry JSON