trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
Later ✕
P0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP2 ExplorerP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suiteoutsidered-only-in-full-suite
- `forge sync` gives git the token only for an https (or loopback) remote on the workbench's own host Later
- The merge queue re-runs a batch's budget-only reds once, serially, before calling it red — budget tests under gate load are sinking 8-pull batches Later
- Config files open as a form: JSON edited through a clean, typed UI that commits or proposes Later
- Files render in the browser: CSV/TSV as a real table — sticky header, sort, filter, row count Later
- Files render in the browser: audio and video play inline, seekable Later
- Files render in the browser: images and SVG inline, fit to the pane, with zoom and their real size Later
- The terminal's pull screen offers Take back on a shipped pull, as the page does Later
- deleteRepo orphans files when rm fails partway: presence is keyed on HEAD, not the directory Later
- Repo-wide rule tests (raw ms budgets, migration pins) skip a pull's own check, so rule breakers go green and sink merge batches (5 pulls today) Later
- Builder routing: rebases go to a builder who can't push (0/5 ok), and the picker sends 23 of 23 picks to Scout (5 slots run 1 builder) Later
- Forge releases go dark: the deploy has maxSurge 0 with a 720 s drain, and a failed release deadlocks the quota; surge instead (maxUnavailable 0) Later
- Builders push migrations without their pin and sink merge batches: the crew's pre-push runs pin-migrations automatically when a migration changes Later
- The repo home batches its visibility, sealed and issue-by-id probes for pulls and runs Later
- README is 300 bytes from its 60 KB budget, so every README addition turns its pull red: move Develop and What works today into docs/ (target 45 KB) Later
- Public page defects for guests: /flow redirects to a /boards 404, doubled forge title suffix, JSON 404 on the releases page, slow openapi.json Later
- releases.json misses the tag-based releases 0.7.272 to 0.7.274, so standings and the behind watch can't see new releases Later
- During a rollout an app's host briefly serves forge pages (title forge, forge 404s) beside the app; app hosts must never fall through to the forge router Later
- A rollout must not turn in-flight gates red: an interrupted gate re-runs as the same candidate, and red (check) retries once before bisecting Later
- Bigger merge batches: queue.batch as a capacity setting (was the constant 8), and the batch grows after green gates and halves after a red Later
- A release never moves main: the release record leaves the tree, and a base move disjoint from a gate does not void it Later
new above
offline