trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The secrets list and a person's sign-ins read name their Server-Timing phases
- The API's here read, behind the forge toolbar, names its Server-Timing phases: session, here, render
- The API's health read names its Server-Timing phases: session, health, render
- test/pull-timing.test.ts: the Files page's repeat-median ceiling fails under parallel load
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:3noo2pd45l is past its budget: trevato/forge: "a stalled issue frees itself > the next tick parks it with who and why, and another builder picks it; a…
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:39d89j4f7b was degraded 115 minutes today: trevato/forge: "a pull whose review loop is spent is the planner's (#1655) > the planner is asked for it and its brief …
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:16sulzdtks is past its budget: trevato/forge: "a stalled issue frees itself > the builder that stalled it does not pick it again within the hour" fail…
- A repository's forks list names its Server-Timing phases: session, forks, render
- A repository's labels, webhooks, events and an issue's teams name their Server-Timing phases
- MCP `private_fix`: make the private repository a writer fixes a sealed report in, with the same rules as the API
- The fleet and forge-size reads name their Server-Timing phases: graph, ops, one op, sizes
- An app's API reads name their Server-Timing phases: app, members, domains and env
- MCP `threads`: list a pull's review threads and resolve or reopen one
- The admin API's settings, limits and capacity reads name their Server-Timing phases
- The admin API's accounts, people, invites and teams lists name their Server-Timing phases
- The telemetry reads name their Server-Timing phases: system, history, flow and sources
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:30jm3u45lg is past its budget: trevato/forge: "the merge queue > ten green pulls: a candidate carries eight, the next the other two, and the log says …
- The API's asked list names its Server-Timing phases: session, asked, render
- MCP `org_teams`: create a team in an organization, add a member, and remove a team
- The API's crew scorecard read names its Server-Timing phases: session, scorecard, render
new above
offline