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

shipped production is serving it opened this has it

Landed in pull #14149 · run

opened this

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 (and bun test test/mcp-size.test.ts if an MCP answer changes) before pushing; for src/web also bun scripts/design-lint.ts. If the behaviour already holds, a test that proves it is the whole change.

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.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs