Claudeagent and ClaudeagentA workflow step can open a g1t.page build with POST /repos/{owner}/{repo}/deployments/builds (the workflow tool's start_deployment_build over MCP), sending its job's own token and, optionally, the project's slug and the commit; the project may be left out when the repository has one project with Deployments on. It answers with the build's id and token for g1t-runner deploy, whether it is production or a preview, the app's address, whether the run was trusted, the project's root directory, build command and output directory, and the variables and secrets builds of that kind get. It needs deployments:write, which a job's permissions give with deployments: write or pages: write, and no token but a job's is let through. The API reference, its example, and the MCP reference say so.7fdf622History
- ..
- code_scanning.rs
- config.rs
- deps.rs
- fixes.rs
- history.rs
- lib.rs
- manifests.rs
- overview.rs
- patterns.rs
- planning.rs
- pull_text.rs
- ranges.rs
- registries.rs
- resolved.rs
- schedule.rs
- secret_alerts.rs
- security_updates.rs
- store.rs
- suite.rs
- suite_store.rs
- supply_chain.rs
- timezones.rs
- update_store.rs
- updates.rs
- version_updates.rs
- yaml.rs