trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The terminal's Usage screen opens the fleet graph with `f`: your repositories' spend and runs per hour over 24 h and per day over 14 d
- The forge ships itself: a landing goes live in seconds with no image, no Forgejo, no Kubernetes roll and no steward
- Each label on Settings › Labels says how many open issues and pulls carry it, as a link to the issues list narrowed to it
- The terminal lists your passkeys, with name, added and last used, beside SSH keys
- Home is the living pipeline: KPIs, what is moving, what shipped, your apps, and one box to tell the crew
- Removing your last passkey is refused when the account has no password, on Settings and through MCP alike
- The terminal's board screen removes the marked panel with `x` after `remove <title>? y/n`, as the web's Remove does
- An admin stops running a repository as an app from the terminal's Deploys screen with `X`, after typing its name, as Settings' Stop running as an app does
- Remove on a board panel goes through the confirm page, which names the panel, and refuses if the board changed underneath
- A test fails when a terminal screen calls a destructive action without asking first
- The terminal's New forge screen picks a template, Blank or Starter app, as MCP spawn's `template` does
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2hvdu8l540 is past its budget: trevato/forge: "after a write, signed-in home is answered from memory within the budget and says what to swap" failed o…
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:31u5r0o0wi is past its budget: trevato/forge: "no GET route answers 200 without a session phase unless the allowlist names it" failed on 3 pulls in th…
- A hosted child forge has no crew runner: its issues are never picked up
- GET /api/v1/releases answers the kept releases, and ?shipped=true what went live, as MCP `releases` does
- GET /api/v1/admin/drills answers each failure domain's last drill, verdict and command, as MCP `drills` does
- A merge conflict is not a failed try: the pull is brought up to date and its tries are kept
- GET /api/v1/flags answers every declared flag with why, default, owner issue and live value, as MCP `flags` does
- An admin runs a restore drill from the terminal's Resilience dialog with `r`, after a y/n, and reads the verdict there in the Backups page's words
- An admin renames or recolours a label from the terminal's Labels screen with `e`
- Remove on a cloud account goes through the confirm page, which names the account and says its sealed token goes with it
new above
offline