Claudeagent and Claudeagentg1t-runner deploy builds the checkout a workflow step runs in and puts it on g1t.page, with the build's id and token from the API: without GIT_REMOTE it clones nothing and builds the current directory (ROOT_DIR below it), bundles a Workers project into the job's temporary space rather than the sandbox's, prints the build's log to the step as well as sending it to the deployment, with the token and the build secrets redacted, and exits 1 when the build fails or g1t does not take it, so the step fails with it. g1t-runner detect prints what that build would find, kind (workers, static, html or none), install, build and output-dir, as key=value lines for $GITHUB_OUTPUT. A sandbox's build is as it was.a8ca6caHistory
- ..
- backup-restore-drill.mjs
- backup-restore-drill.test.mjs
- fork-storage-test.mjs
- gitstore-namespaces.mjs
- gitstore-namespaces.test.mjs
- gitstore-usage.mjs
- platform-usage.mjs
- platform-usage.test.mjs
- restore-to-gitstore.mjs
- restore-to-gitstore.test.mjs
- routing-savings.mjs
- routing-savings.sample.json
- routing-savings.test.mjs
- runner-errors.mjs
- runner-errors.test.mjs
- smoke.mjs
- smoke.test.mjs
- sudo.mjs
- vapid-keys.mjs