trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Full suite red: test/hollow-cli.test.ts
- Full suite red: test/hollow.test.ts
- src/core/repos.ts has the reads a display lists from: listAdminOwnedRepos, readableRepoIds, repoDatesFor and listAllReposByOwner
- A pin's screenshots get a gallery page on the builds page
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1p9qyksd9g is past its budget: trevato/forge: "the page with 150 repositories costs a handful of statements, not one per repository" failed on 3 pulls…
- GET /api/v1/conversations carries an ETag and answers a repeat with 304 until one of the viewer's conversations changes
- GET /api/v1/repos/:owner/:name/following/proposals carries an ETag and answers a repeat with 304 until a proposal to the parent changes
- Full suite red: test/work-branch.test.ts
- GET /api/v1/repos/:owner/:name/app/notes carries an ETag and answers a repeat with 304 until a note arrives or is moderated
- GET /api/v1/repos/:owner/:name/builds/:label/shots/looks carries an ETag and answers a repeat with 304 until a new look of the pin's commit is taken
- GET /api/v1/repos/:owner/:name/builds/:label/shots carries an ETag and answers a repeat with 304 until a shot is added, removed or reordered
- GET /api/v1/conversation/turns carries an ETag and answers a repeat with 304 until a turn, a queued message or the running state changes
- The owner's bets page fits a 390 px phone: no sideways scroll and no proposed bet card taller than the screen
- GET /api/v1/agents and /api/v1/agents/:username carry an ETag and answer a repeat with 304 until an agent is added, changed or removed
- Jay Moran's pin demos are on main: src/actions/pin_demos.ts, with launchOf in src/git/builds.ts
- A cart nobody gave a cover still has one: Jay Moran's src/arcade/cover.ts and cover-template.png are on main and tested
- Activity wording for build.shots events
- Forks copy a pin's refs/shots with its refs/builds
- GET /api/v1/repos/:owner/:name/upstream carries an ETag and answers a repeat with 304 until the outside upstream or its last check changes
new above
offline