trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- GET /api/v1/repos/:owner/:name/tags carries an ETag and answers a repeat with 304 until a tag is added, moved or deleted
- GET /api/v1/repos/:owner/:name/branches carries an ETag and answers a repeat with 304 until a ref moves
- GET /api/v1/repos/:owner/:name/map carries an ETag and answers a repeat with 304 while the map snapshot has not changed
- GET /api/v1/repos/:owner/:name/runs carries an ETag and answers a repeat with 304 until a run in the page starts, moves or finishes
- GET /api/v1/users/:username/repos carries an ETag and answers a repeat with 304 when none of that person's repositories it lists has changed
- GET /api/v1/forges answers the client list the /forges page and the MCP forges tool show: claimed, running, spend, what needs attention and the next step
- An agent reads a fork family's iterations through an MCP iterations tool, as GET /api/v1/repos/:owner/:name/iterations does
- GET /api/v1/repos/:owner/:name/issues/:number carries an ETag and answers a repeat with 304 until the issue changes
- Every MCP tool's doc names each argument its inputSchema takes, and a test refuses a tool whose doc leaves one out
- GET /api/v1/repos/:owner/:name/pulls/:number carries an ETag and answers a repeat with 304 until the pull's head, checks, review or state change
- GET /api/v1/repos/:owner/:name/iterations answers the fork family's runs and pins as JSON, the same the Iterations page draws
- A test runs the toolbar pill's script and proves it draws one freshness line under "Preview of pull #N" for a merged, closed, deploying or behind preview, and nothing for an open, current one
- An app's page served with the forge toolbar keeps a validator, so a signed-out revisit is a 304 instead of the whole page
- Iterations is Jay's actual page, with his name on it: the landed version is a smaller rewrite
- GET /api/v1/releases?shipped=true carries an ETag and answers a repeat with 304 until something new goes live
- GET /api/v1/repos/:owner/:name/issues/:number/comments carries an ETag and answers a repeat with 304 until a comment is added or edited
- GET /api/v1/repos/:owner/:name/builds carries an ETag and answers a repeat with 304 when no pin has changed
- Explore says when an updated:, archived: or owner: word is not one it takes, instead of matching nothing as text
- GET /api/v1/repos/:owner/:name/forks gives each fork's ahead, behind and last push, and the parent, as the forks page and the MCP forks tool do
- GET /api/v1/changelog carries an ETag and answers a repeat with 304, as /changelog.atom already does
- GET /api/v1/repos carries an ETag and answers a repeat with 304 when no repository it lists has changed
- GET /api/v1/repos/:owner/:name/pulls carries an ETag and answers a repeat with 304 when the list it would send has not changed
- GET /api/v1/repos/:owner/:name/issues carries an ETag and answers a repeat with 304 when the list it would send has not changed
new above
offline