[Schema Inaccuracy] Wrong media types in rest/gists/comments.md

Open Beginner friendly
#5,869 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
openapi
Domain
documentation

Research direction

Open rest/gists/comments.md and compare its documented media types with the reported API behavior. Remove the inaccurate base64 media type entry, then verify the rendered Gists comments documentation no longer claims that encoding is available.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

The media types are wrong on the page https://docs.github.com/en/rest/gists/comments

The docs claim there to be a "base64" encoding, but there is none, and there hasn't been such encoding for more than 3 years, possibly since forever.

Expected

Remove the inaccurate documentation. The base64 feature is not available, and hasn't been available for at least 3 years, possibly has never been available.

Reproduction Steps

$ date --utc && curl --silent -H "Accept: application/vnd.github.base64+json" https://api.github.com/gists/9257657/comments/1221189 | grep body 
Thu  8 Jan 19:20:52 UTC 2026
  "body": "Thanks, Octocat!\n"
Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
3h 33m
Merged PRs (30d)
51

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.