trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Land the warming-files line from branch scout/6547-a-pure-read-names-the-files-that-gained, with its history tested and each line naming its repository
- A builder's clone has its dependencies installed before the run starts, so the type check always has its types
- A planner's "one more round" comment on a handed-over crew pull gives it back to its builder
- A reviewer asks for everything in one round, and a later round reviews only what changed and whether its earlier asks were met
- A builder run that declines as "already done on main in <commit>" posts that note on its issue and stops further runs on it
- A pure read groups the last 24 h of declined build runs by reason, so planning mistakes show as a count
- An issue never has two build runs at once: a second dispatch while one runs, or within 10 minutes of its pull opening, is refused
- The decider never closes a pull while its builder's run is still running; it waits for the run to end
- `bun scripts/fast.ts` prints the test files the fast tier would run for the working tree's diff against main
- /forges: an owner's forges side by side, with size, use against size, apps and last heartbeat
- A changes-asked review post ranks above an approval of the same age on home
- Every search input sizes by one base rule, and `.search` leaves the stylesheet
- The home timeline draws a day divider before the first post of each UTC day, never twice
- A pure function turns a day's feed events into at most three digest lines, one per repository, biggest change first, each with its evidence link
- A pure read says, per repository, how many approved pulls wait for the merge queue and how long the oldest has waited
- Land the 3-day-conflicted crew pull sweep from branch scout/5940-a-crew-pull-that-has-stayed-conflicted-f, with its event kind classified for its audience
- A pure read estimates when an approved pull lands, from its place in the queue and the recent landing pace
- A pure read names the tests failing on three or more open pulls: a clash between pulls, not separate bugs
- A pure read lists the pairs of open pulls that touch the same files, most files shared first
- A pull the queue holds as red alone says so on its page: "red alone at <time>, waiting for a new head or a new main"
- A pure read picks the five most-behind open crew pulls to bring up to date first
new above
offline