trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- README.md is a front door under 60 KB: what the forge is, how to run it, and a linked index into docs/
- A signed-out 404 offers Go home and Explore beside Sign in
- The pill joins the other side's origin to this page's path, so a `//` path stays on the app
- `/__forge/crew` hands a reader the app's other side, and a guest of a private app gets none
- finishing still silent after #6239: the 20 conflicted pulls are dropped before the logged branch; log every early continue and make the conflict tests agree
- A failed check's one-line summary names up to three failing tests and how many more, not only the first
- The finishing pass's conflicted pulls stay with the forge that found them: `conflictedPulls` of one database never reads another's
- A repository's files page draws its README's first 64 KB like the home does: trevato/forge/tree/main under 150 KB
- A repository's map draws only open issues by default, and a "Show done" link draws the rest: trevato/forge's /map under 400 KB
- A map's share card resolves under 150 ms and draws under 300 KB for 2,000 closed and 300 open issues
- The shelf's stretches show in Server-Timing on /, /apps and a person's page
- A vision pull shows the direction it will write, and Settings marks which part follows the vision and which is the owner's
- /explore's rank stays warm on the live forge: a meter or heartbeat write no longer throws the ranking away
- An issues list reads every row's status word in one batch: `words` under 5 ms for a page of issues
- GET /api/v1/feed answers 304 only when nothing the viewer would read has changed: events, shares, dismissals, mutes, chips and the minute
- Sentinel: disk was degraded 1072 minutes today: Disk is nearly full: 9% free.
- finishing.ts says why it skips each approved, conflicted pull (log line + tick field): 21 have waited 3 h with nothing queued
new above
offline