Wiki API: content_base64 empty in POST/PATCH responses #607

New Issue

2026-06-11T21:42:45Z

jmiller commented

2026-06-11 21:42:45 +00:00

Summary

When creating or updating a wiki page via the API, the response always returns "content_base64": "" even though the content was written successfully.

Steps to Reproduce

Create a wiki page:

POST /api/v1/repos/:owner/:repo/wiki/new
{ "title": "Home", "content": "# Hello", "message": "Create page" }

Response includes "content_base64": "" — empty string
Same behavior with PATCH updates to existing pages
A subsequent GET also returns "content_base64": "" in some cases

Expected Behavior

The response should include the page content in content_base64 so the caller can verify the write succeeded without a separate request.

Actual Behavior

content_base64 is always an empty string in write responses. The content is written correctly (visible in web UI), but the API response doesn't reflect it.

Impact

API consumers cannot verify wiki writes succeeded without cloning the wiki git repo or checking the web UI. Makes it difficult to build reliable wiki automation.

## Summary When creating or updating a wiki page via the API, the response always returns `"content_base64": ""` even though the content was written successfully. ## Steps to Reproduce 1. Create a wiki page: ``` POST /api/v1/repos/:owner/:repo/wiki/new { "title": "Home", "content": "# Hello", "message": "Create page" } ``` 2. Response includes `"content_base64": ""` — empty string 3. Same behavior with PATCH updates to existing pages 4. A subsequent GET also returns `"content_base64": ""` in some cases ## Expected Behavior The response should include the page content in `content_base64` so the caller can verify the write succeeded without a separate request. ## Actual Behavior `content_base64` is always an empty string in write responses. The content is written correctly (visible in web UI), but the API response doesn't reflect it. ## Impact API consumers cannot verify wiki writes succeeded without cloning the wiki git repo or checking the web UI. Makes it difficult to build reliable wiki automation.

jmiller referenced this issue from a commit

2026-06-11 21:56:45 +00:00

fix: wiki API sub-page support and content response (#606, #607)

jmiller referenced a pull request that will close this issue

2026-06-11 21:57:00 +00:00

fix: wiki API sub-page support and content response (#606, #607) #608

jmiller closed this issue

2026-06-11 22:17:09 +00:00

jmiller referenced this issue from a commit

2026-06-11 22:18:58 +00:00

Merge pull request 'fix: wiki API sub-page support and content response (#606, #607)' (#608) from fix/606-607-wiki-api-bugs into main

Sign in to join this conversation.