trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A fork with an archived parent drops the 'following · N ahead' badge, and an admin can detach a fork from its parent
- The terminal's limbs screen says what the planner changed on a re-planned limb: each old issue and what replaced it, as the milestones page does
- The terminal's About card opens the repository's events with `v`: newest first, paged, as MCP `events` reads them
- The terminal lists the forge's limits with value, default and bounds, and a forge admin changes one after a plan, as MCP `limits` does
- The terminal makes an organization you own from the palette, with the same rules and words as MCP `org_create`
- The terminal sets, reads or turns off your phone notify URL, showing only its host, as MCP `notify` does
- `forge search <words>` finds code, issues and pulls across the repositories you can read, as /api/v1/search does
- The blob page draws a PDF, image or video over 1 MB: its kind is read from the first bytes, never the whole file
- The Claude Code and OpenCode plugins' `asked [app]` says what you asked the crew and what became of each, through MCP `asked`
- MCP `asked` draws a card in MCP Apps hosts: what you asked the crew, its state and the pull that closes it
- `forge asks --ship/--close/--dismiss <n…>` decides asks from the shell: planned first, applied after a y/N, as POST /api/v1/asks/bulk
- The terminal lists the forge's capacity and guards live, and a forge admin changes a settable one after a plan, as MCP `capacity` does
- The terminal's sign-ins screen revokes one of your API tokens with `d` after a confirm, never showing the token
- The /api/v1/repos/:owner/:name/issues routes move out of src/http/api.ts into src/http/api/issues.ts, unchanged
- The /api/v1/user routes move out of src/http/api.ts into src/http/api/user.ts, unchanged
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:fxc21whost is past its budget: trevato/forge: "the merge queue gates a red (check) once more before it searches > red (check) once, then green: the ba…
- test/merge-queue-check-retry.test.ts passes every time in the full suite, not just alone
- POST …/plan answers which opened issues will not start yet and why: a hot file, a pin or an open pull
- The terminal's deploys screen lets a writer see who a private app names with `m`, and add or remove one after a plan, as MCP `app_members` does
- The planner's brief names the files that are hot now, with their pull counts, so it plans around them
new above
offline