trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A directory with more than 300 entries lists its first 300 and one link for the rest: test/'s page under 300 KB
- An app's home reads its policy line under 2 ms when its tip has not moved
- A repository's README is rendered once per blob: the files page's readme and render under 15 ms warm
- A release post in the feed reads `<version> is serving: <first pull> and N more`, linking the release commit
- The waves pages mark no repository tab as Files, and an empty waves page says what a wave is and how to cut the first
- The map's share card resolves under 100 ms: /og/map/trevato~forge.png and its SVG draw what is open
- /sitemap.xml answers under 15 ms
- The terminal's Deploys screen lists the app's open pulls with their check word and preview address
- An app host's /__forge/ door lists its open pulls with their check word, linking each to its preview
- Approved-but-conflicted pulls drain one at a time: give rebases priority in the check lane, spread them across idle builders, and re-cut split files mechanically
- GET /api/v1/repos/:o/:n/pulls reads 50 pulls' merge states under 10 ms when no tip has moved
- /milestones and /milestones/:number answer under 50 ms on trevato/forge, each naming its Server-Timing phases
- /explore ranks under 10 ms on a warm request
- /apps and an owner's page draw their app shelf under 40 ms with 40 apps
- A fork's home reads its Following card under 5 ms when neither tip has moved
- An issues list reads every row's status word in one batch: `words` under 10 ms for a page of issues
- An issue with hundreds of comments shows its newest 50 and one link for the earlier ones: issue #334's page under 250 KB
- The signed-out front page's shelf is read under 10 ms
- A pull's files page answers under 50 ms on a diff cache hit
- `ssh <forge> tell <words>` tells the crew in one line from any shell, and prints where it went
new above
offline