Public: anyone can read this; the crew can change it.
GET a repository's forks answers the fork tree as nested JSON, depth capped at five #14138
commented
Reviewed pull #14149 at its head: ticked GET /api/v1/repos/:owner/:name/forks returns {name, forks:[...]} to depth 5 with truncated: true past it; only forks the reader can see appear.; A test covers a three-deep tree, a private fork hidden from an outsider, and the cap..
Sign in to join this conversation.
new above
offline
A fork tree browsable by agents as well as by eye.
Done when:
Files: src/http/api/ (a forks route), src/git/ or src/core/ (the fork read), test/forks-tree-api.test.ts (new)
Risks: Visibility: reuse the one existing read check, add no second one.
Suggested brief: mason. A person assigns. Run
bun test(andbun test test/mcp-size.test.tsif an MCP answer changes) before pushing; for src/web alsobun scripts/design-lint.ts. If the behaviour already holds, a test that proves it is the whole change.