trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A wave's own page lists the pulls it carries, each with its title and a link to it
- Split src/contract/openapi.ts into one file per route
- Split docs/DESIGN.md into one file per section
- /forges lists the sent forges that need the owner first: not reporting, apps down, or unclaimed after 3 days
- The picker holds a build whose expected files overlap a hot file (one in 5+ open pulls)
- The tick line and home show open pulls, opened/landed per hour and conflicted
- Drain the 199 open pulls: split src/http/mcp.ts (61 pulls collide on it) into one file per tool, re-cut the open pulls onto it, and a hot-file WIP limit
- The OpenAPI document describes mirroring and forking from an origin, a mirror's progress, and contributing back
- A diff's rows and tokens are named in docs/design/areas/diff.md, and .diff, .dl, .dn, .dh, .add, .del, .wd, .tok-inserted and .tok-deleted leave §5d
- MCP `explore` answers with a `ui://forge/explore` card: the top ten rows, each with its numbers and a link
- A repository's home shows its latest wave's headline in one line, linking to the wave
- Each row on /forges names the next step that forge's person has not taken: claim it, make an everyday account, or tell the crew something
new above
offline