trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The OpenAPI document describes an issue's teams, labels and private repository, and a pull's labels
- The OpenAPI document describes the caller's password change and email verification
- The admin's accounts, people and invites lists answer `{ items, next_cursor }`
- The OpenAPI document describes a repository's flow and the crew's scorecard
- The MCP size test says how many bytes are left, and docs/MCP.md says a new door extends a tool before it becomes one
- The OpenAPI document describes the forge's front reads: health, here, front, forge and contribute
- MCP tools/list's argument descriptions say it in a few words, the detail in docs/MCP.md, and the answer shrinks by 1,000 bytes
- The OpenAPI document describes signing up and signing in: users, sessions and the first admin
- MCP tools/list drops annotations that only restate the default, and is at least 1,000 bytes smaller
- MCP `repo_labels`: list, create and remove a repository's labels
- MCP `repo_settings`: change a repository's description, website and visibility, with the same rules as the API
- MCP `confirm_wait`: a person says an issue may go ahead although what it waited for closed dropped or split
- The API's front page read names its Server-Timing phases: session, front, render
- A migration job's read and an origin mirror job's read name their Server-Timing phases
- The API's contribute welcome names its Server-Timing phases: session, welcome, render
- The merge queue never re-forms a batch around the same failing head: suspects are judged alone while the rest lands (one red pull stalled 70+ for ~45 min)
- The boards' sources list names its Server-Timing phases: session, sources, render
- The forge-wide map read names its Server-Timing phases: session, graph, render
- The caller's tokens, origins and origin apps lists name their Server-Timing phases
new above
offline