sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

GitHub GraphQL adds issue comment pinning and pin status

Introduced 2026-03-12 · score 0.99

HOW TO USE IT

When pinning a comment on an issue, call `pinIssueComment` with the comment’s node ID; use `IssueComment`’s `Pinnable` fields and the issue’s `pinnedIssueComment` to inspect pin status and details. Comment pinning is not supported on pull requests.

mutation { pinIssueComment(input: { issueCommentId: "<ISSUE_COMMENT_NODE_ID>" }) { issueComment { id isPinned pinnedAt pinnedBy { login } viewerCanPin viewerCanUnpin } } }
query { node(id: "<ISSUE_NODE_ID>") { ... on Issue { pinnedIssueComment { issue { id } issueComment { id } pinnedAt pinnedBy { login } } } } }

WHY THIS HELPS

Pin or inspect pinned issue comments through the GitHub GraphQL API.

REQUIREMENTS AND LIMITATIONS

  • PinIssueCommentInput.issueCommentId (required): ID of the issue comment to pin; comment pinning is unsupported on pull requests.
  • PinIssueCommentInput.clientMutationId: Unique identifier for the client performing the mutation.
  • Pinnable.isPinned: Whether the entity is currently pinned.
  • Pinnable.pinnedAt: When the entity was pinned.
  • Pinnable.pinnedBy: User who pinned the entity.
  • Pinnable.viewerCanPin: Whether the current viewer can pin the entity.
  • Pinnable.viewerCanUnpin: Whether the current viewer can unpin the entity.
  • PinnedIssueComment.issue: Issue the pinned comment belongs to.
  • PinnedIssueComment.issueComment: Comment that was pinned.
  • PinnedIssueComment.pinnedAt: When the comment was pinned.
  • PinnedIssueComment.pinnedBy: Actor who pinned the comment.
  • Prerequisite: The target must be an issue comment; GitHub documents that comment pinning is not supported on pull requests.
  • The `PinIssueComment` input requires `issueCommentId`.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card