trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
P3 Fork tree
171 of 176 done
5 open · 32 merged in 7 days · moved
About 2 days at this week's pace: 33 closed in 7 days, 5 open.
Limbs
Blocked
Merged in 7 days
- small: The fork tree names how each fork follows its upstream in one word
- MCP `forks` answers one fork's upstream and downstream chain in plain words, with the link to each page
- The fork tree page links each node to its fork's page and marks the one you are in
40 more merged
- Severing a fork from its upstream asks one confirm that says what stays and what stops, and is receipted
- A fork's page says in one plain line how it follows its upstream and when it last took from it
- MCP `explore` gains a `tree` view: an app's fork chain in the page's own words, no new tool
- small: a forge's first-login page names the crew working in plain words, with no developer terms
- The MCP fork_tree tool answers with a `ui://forge/forks` card: each fork as a row with its depth and how it follows
- The MCP boards tool answers with a `ui://forge/board` card: a board's panels as rows, with the same numbers as the page
- A mirrored repository's credit (upstream, licence, original authors) is in the REST and MCP answers, not only on its page
- A fork's page says in one line how it follows its upstream and an admin switches it in one tap
- A fork tree reader returns an app's ancestors, siblings and descendants as plain data, filtered by what the caller may read
- A test proves a failed recombine shows its sentence on the combined card and clears once main is fixed
- A failed recombine leaves the combined card stale with the failure's sentence, and the docs stop saying main alone does not recombine
- A push to main alone starts the recombine pass, after the hook has answered
- One call rebuilds combined/N for every open kept-fork pull into the default branch
- A frozen mirror says so in one line on its repository page, not in a boxed card
- A kept fork's pull is checked on its combined commit, so its green is the green of what lands
- A fork's Following card and its forks lineage speak the home page's language
- A repository's Flows page, what flows in and out, speaks the home page's language
- A conflicted pull's resolve page speaks the home page's language
- A pull's looks open with one line counting the pages shown beside main and those main has no picture of
- The forge's following page speaks the home page's language
- A repository's branches page speaks the home page's language
- A pull's looks show the before and after pairs on a real pull, and say why when main has no picture of a page
- The /family page speaks the home page's language, with looks before and after
- A feature's menu entry carries its declared summary as its title
- A pull's looks show main's picture beside the head's, so before and after are on every pull with no one attaching them
- Settings › Features speaks the home page's language
- An admin reaches Settings › Features from the page of an app that declares a feature, and the empty state links the docs
- When a pull lands, its head's looks are kept as main's looks for each page, width and theme
- bench/results records the flows view at 200 lines: warm p50 and p95 against the 50 ms budget
- The flows view is a picture first: sources on one side, followers on the other, in the home page's language
- An admin sees flows across all repositories in one view
- Act on a flow line where it stands: update a dependency, follow or stop, pull a change in, send it back
- The /family page fits a 390 px phone: the fork tree scrolls inside its own box, the page never scrolls sideways
- The radar reads upstream releases on a schedule and files an issue when an update is worth taking, with the reason and the risk
- The flows view shows every line in and out: dependencies with advisories, origins, followed sources, forks, followers, mirrors and forges that follow
- docs/DESIGN.md opens with the design principles in under 30 lines, with the home page and Security settings as worked examples
- A display launches into the arcade host, playable by keyboard and on a phone
- A display's builds are chosen through PUT …/display/builds, validated and same-origin checked
- `/:owner/:name/display` shows a repository's display on main, read-only
- `/displays` lists every display the viewer may read, on main
Issues
165 closed
-
.repo-lineage leaves the stylesheet #4604 done
-
Take updates from trevato/forge-upstream #1303 not doing
-
.repo-lineage leaves the stylesheet and docs/DESIGN.md §5d #4229 not doing
-
.steps leaves the stylesheet and docs/DESIGN.md §5d #4303 not doing