trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The new-forge repository picker stays fast and usable with 150 repositories
- Build pins: port Jay Moran's git/builds.ts, notesIntent and the pin pages onto main
- Home says the week's percent left and when it runs out at this pace
- Backups leave the platform: one last copy of the 36 GB Forgejo dump, the lanes retired one by one, and a restore that never touches it
- With `signin.edge` off the owner signs in by passkey, and Settings → Capacity turns it back on
- A restore drill script restores a snapshot onto the forge box from the bucket alone and compares counts with production
- Settings → Capacity flags a crew concurrency set below its ceiling and resets it in one click
- One night of the forge's flake hunt and outside gate is compared with Forgejo's, and the result is written down
- After a fork's pull lands in slices, the author's `git merge main` is clean, proven with two forges
- Bring in Jay Moran's build pins and Iterations, ported onto main with his name on them
- A pull opened on the Forgejo mirror reaches trunk as a real pull with its author, and the mirror stays a plain copy
- A test proves a guest pull's check runs with no secrets, and has them after a person approves
- The metrics page shows main-thread stall time by route, so a fix's before and after reads from the forge itself
- A merge from a followed source can't land without its content
- Sentinel: release was degraded 1090 minutes today: Release 0.7.354 is unproven: https://forge.open-platform.sh/boards as desktop /boards took 1031 ms, over 1000 ms (statu…
- Flake hunt and outside gate run from the forge on their schedule and file what the Forgejo jobs filed
- A big pull from a fork lands in reviewed slices and still ends as a merge of the author's head
- Before a fork's pull merges, its preview runs the combined build, and conflicts are resolved in a branch on our side with the decisions written for the author
- The flake admission rule catches a test that waits on time: close the gap that let tui-backups and conversation-queue in
- No account depends on the platform's sign-in: every edge-made account gets a passkey, then the edge can be switched off
- A box of the forge's own runs a restored snapshot as a service, beside production, taking no traffic
new above
offline