We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 31 since January 2026, each linked to its source.
github-graphql-apiWhen querying GitHub Security Advisories, pass `isWithdrawn` and/or `severities` to filter results, then select the advisory metadata fields you need.
query { securityAdvisories(isWithdrawn: true, severities: [HIGH, CRITICAL], first: 100) { nodes { cveId githubReviewedAt nvdPublishedAt repositoryAdvisoryUrl sourceCodeLocation } } }When you need to rerequest pull request reviews, call `rerequestReviews` with the pull request’s Node ID and any reviewer Node IDs; select the returned payload fields you need.
mutation RerequestReviews($input: RerequestReviewsInput!) { rerequestReviews(input: $input) { actor { __typename } clientMutationId pullRequest { id } requestedReviewersEdge { node { __typename } } } }
# Variables: {"input":{"pullRequestId":"<PULL_REQUEST_NODE_ID>","userIds":["<USER_NODE_ID>"],"teamIds":["<TEAM_NODE_ID>"],"botIds":["<BOT_NODE_ID>"]}}When managing related issues through GitHub’s GraphQL API, query `Issue.relatesTo` with pagination and ordering, or use `addRelatesTo` and `removeRelatesTo` to change a relationship.
query { node(id: "<issue-id>") { ... on Issue { relatesTo(first: 20, orderBy: {field: RELATES_TO_ADDED_AT, direction: DESC}) { nodes { id } pageInfo { endCursor hasNextPage } } } } }When configuring a repository ruleset through GraphQL, set `RuleParametersInput.codeCoverage` for coverage thresholds or `codeQuality` for review severity; specify only one field in `RuleParametersInput`.
When linking pull requests as manual closing references, call `addCloseIssueReferences` on an issue with the issue ID and up to 10 pull request IDs. Select the returned `issue` to read the updated issue.
mutation { addCloseIssueReferences(input: { issueId: "<issue-node-id>", pullRequestIds: ["<pull-request-node-id>"] }) { issue { id } } }When resolving a pull request review thread, pass `resolutionReason` in `ResolveReviewThreadInput` to record why it was resolved.
mutation { resolveReviewThread(input: { threadId: "<thread-node-id>", resolutionReason: ADDRESSED }) { thread { isResolved } } }When updating an issue’s field values, use `updateIssue` with `issueFieldUpdates`; each entry names the field and operation, and may include a value. Choose `ADD`, `CLEAR`, `REMOVE`, or `SET` according to the documented operation behavior.
mutation { updateIssue(input: { id: "<issue-node-id>", issueFieldUpdates: [{ fieldName: "<field-name>", operation: SET, value: "<value>" }] }) { issue { id } } }When maintaining issue triage by project field values, filter the repository’s issues with `IssueFilters.issueFieldValues` and provide exactly one field selector and one value filter per filter object.
query { repository(owner: "<owner>", name: "<repo>") { issues(first: 100, filterBy: { issueFieldValues: [{ fieldName: "<field-name>", textValue: "<text>" }] }) { nodes { id title } } } }When deleting a view from a GitHub project, call `deleteProjectV2View` with its view ID. The mutation returns the deleted view in `projectV2View`.
mutation { deleteProjectV2View(input: {viewId: "<VIEW_ID>"}) { projectV2View { id } } }When a GitHub Project view needs a new name, filter, or layout, call `updateProjectV2View` with its required `viewId` and the fields to change. Select `projectV2View` from the mutation payload to get the updated view.
gh api graphql -f query='mutation { updateProjectV2View(input: {viewId: "<VIEW_ID>", name: "<NAME>", filter: "<FILTER>", layout: TABLE_LAYOUT}) { projectV2View { id name layout } } }'