trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Every gate keeps its log, so a red gate can be read without re-running the pull
- When main goes red after a single pull landed, the forge opens a revert pull for it that names the failing test
- A queued merge-queue gate always gets the next free check slot; pull checks never take the last one while a gate waits
- A pure inflow governor: build slots fall while pulls open faster than they land, and rise as the pile drains
- A red merge batch is searched by disjoint halves, never by nested prefixes holding the same suspects
- Every open pull's page says who acts next and why, in one line under its title
- When tools/list passes its size budget, the failing test names the five costliest tools
- A shard killed without naming a test says which test was running and for how long
- The forge computes the "no release" flow alarm (#5930)
- The forge computes the "idle crew" flow alarm (#5930)
- The forge computes the "red main" flow alarm (#5930)
- The forge computes the "stuck pull" flow alarm (#5930)
- An approved pull red for 24 h gets one re-check, then goes back to its builder with the failing test
- The danger zone and repository delete leave settings.ts for src/web/pages/danger.ts
- The kept front page is keyed on a one-row counter the database bumps when the shelf's data changes
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2eynu2flps is past its budget: trevato/forge: "a token that may only read cannot write through any tool > each admin-scope tool is refused for an rw t…
new above
offline