Claudeagent and ClaudeagentA project can build with a workflow. Turning on **Build with a workflow** under Settings, Deployments installs a managed workflow named `g1t` that calls g1t's reusable deploy workflow (`g1t/workflows/.g1t/workflows/deploy.yml@v1`, published from `workflows/` by the actions release) with the project's settings, and pushes and pull requests then start it rather than a build of Deployments' own: the same previews and production, at the same addresses, reported as `g1t / deploy`, now the check of the workflow's job, listed on the Actions page with its runs and logs. A pull request from a fork runs it with a read-only token, as on GitHub, and still gets its preview without the project's build secrets: a read-only job token may open a preview build only from a run of a managed workflow. Fork pull requests run the repository's managed workflows too. Its jobs are Actions time, at cost plus 20% on g1t's machines and free on a self-hosted runner. A workflow named `g1t` in `.g1t/workflows/` takes its place. The deployments and Actions guides say so.41c296aHistory
- backup.test.ts
- backup.ts
- bump.test.ts
- bump.ts
- computer-shape.ts
- computer.test.ts
- computer.ts
- credentials.test.ts
- credentials.ts
- delegate.test.ts
- delegate.ts
- egress.test.ts
- egress.ts
- gate.test.ts
- guard.ts
- hosted.test.ts
- hosted.ts
- hub.ts
- index.ts
- instructions.test.ts
- instructions.ts
- lifecycle.test.ts
- lifecycle.ts
- mentions.test.ts
- mentions.ts
- model-defaults.test.ts
- model-env.test.ts
- model-env.ts
- repo-instructions.ts
- self-hosted.test.ts
- self-hosted.ts
- workflow-hosts.test.ts