trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
LaterP0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP2 ExplorerP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suiteoutsidered-only-in-full-suite
- Terminal: open the private repository a writer fixes a sealed report in Later
- Sentinel: Crew runs in trevato/forge keep failing at the push or the sandbox Later
- While "flow only" is on, a crew pull for a non-flow issue gets no feedback run; it is held with one line saying it waits for the switch P0 Trust
- An admin re-checks, in one call, every open pull whose latest check failed on one named test P0 Trust
- A pure read counts the open pulls from outside the repository's writers, and the oldest one's age P0 Trust
- A pure read says who opened the last hour's pulls: per author, how many, and how many of those serve a flow issue P0 Trust
- A pure read says the time to land: the median and the slowest hours from a pull's opening to its landing over the last 24 h P0 Trust
- The repository map's API names what holds each ready issue: hot_file with the file, run_cap, open_pull and the rest P0 Trust
- A builder whose issue names an MCP tool file is told to run test/mcp-size.test.ts before pushing, and to extend an existing tool rather than add one P0 Trust
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2eynu2flps was degraded 46 minutes today: trevato/forge: "a token that may only read cannot write through any tool > each admin-scope tool is refused for an rw t…
- The flow vitals carry gate minutes and the red-batch rate, and a rate over 30% is named as a miss P0 Trust
- A pure read says the red-batch rate: of the merge-queue gates finished in the last 6 h, how many went red P0 Trust
- A pure read says the gate minutes: check-slot minutes spent on merge-queue gates and on pull checks over the last hour and 6 h P0 Trust
- The flow vitals carry stranded spend, the oldest approved wait, and the red and queued counts, and home, the tick line and MCP `flow` show them P0 Trust
- A pure read counts the open pulls whose check is red, and those queued for a check, as two flow numbers P0 Trust
- A pure read says the oldest approved wait: how long the longest-waiting approved, unlanded pull has waited since its approval P0 Trust
- A pure read says the stranded spend: dollars of crew runs on pulls that are open and not landed P0 Trust
- The boards' flow panel lists the hot files: each file 3 or more open pulls touch, with its count, and the ones at the build limit marked P0 Trust
new above
offline