trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
flow ✕
LaterP0 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 Talkbugfull-suiteoutside
- Connecting a friend's forge is obvious and works with forges on an older release flow
- Iterations is Jay's actual page, with his name on it: the landed version is a smaller rewrite flow
- Bring in Jay Moran's build pins and Iterations, ported onto main with his name on them flow
- Trust does something: Until shows its date, and a repo can follow several trusted forks at once flow
- Two tests turning good pulls red fail on and off on main: make them steady or quarantine them today flow
- GET /api/v1/telemetry/flow never blocks the forge: it held the main thread 19% of the time flow
- Trusted sources fold in by themselves, in real time; everyone else waits for review flow
- A fellow forge owner's work lands cleanly and he can pull back: real merges, kept authorship, no squash across forks flow
- Hotkey hints stay out of the way: shown on hover and on request, never squeezed into the layout flow
- New forge picks its repositories from a searchable multiselect, not a long page of checkboxes flow
- The pacer's burn matches the meter: it says 1.4% an hour while the real meter hasn't moved in over an hour flow
- Bring an app whole from another forge: paste its link, and it runs here flow
- Work crosses forges: pulls, issues and reviews flow both ways, and each side's crew sees them flow
- One forge connects to another as an origin: bring in a friend's app, and stay connected flow
new above
offline