Distillation

🔴 (13:10) User directed that the events_url URI template’s {/privacy} component be replaced with /public to retrieve only public events; omitting it retrieves public events and, when authenticated as that user, private events.

🔴 (13:10) The GET /user private-user response adds private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication; it may also include business_plus and ldap_dn. Both private- and public-user schemas include a plan object with required collaborators, name, space, and private_repos.

🔴 (13:10) GitHub’s private-user and public-user response types are unrelated to the private-profile setting. A token without read:user or user scope still authenticates as its owner, so visibility-sensitive values such as followers and following can differ from an unauthenticated response.

🔴 (13:10) GET /user/{account_id} uses the required integer account_id, a durable user ID rather than a mutable login, and documents 200 and 404 responses.

🔴 (13:10) GitHub’s Emails API can list all of the authenticated user’s email addresses and toggle whether a primary email is publicly visible.

🔴 (13:10) The GET /users response is an array of Simple User objects. Its schema includes optional name, email, starred_at, and user_view_type, plus required account identity and URL fields including login, id, node_id, avatar_url, url, html_url, followers_url, following_url, gists_url, starred_url, subscriptions_url, organizations_url, repos_url, events_url, received_events_url, type, and site_admin.

🔴 (13:10) GET /users/{username} requires the string username handle and documents 200 and 404 responses.

🔴 (13:10) GET /users/{username}/hovercard returns a required contexts array whose objects contain required string fields message and octicon.

🔴 (13:10) The hovercard documentation example uses subject_type=repository and subject_id=1300192 to obtain contextual information about octocat as owner of the Spoon-Knife repository.