Claudeagent and ClaudeagentA g1t.page build opened by a workflow job no longer stays Building for 45 minutes when the job is cancelled. Whenever a job that ran ends, with any conclusion, the actions service tells deployments (`workflow_job_ended`), which fails every build that job opened with `start_from_workflow` and left queued or building, saying how the job ended ("The workflow job was cancelled before the build finished."), with the commit's `g1t / deploy` check and `deployment.failed` as for any failed build; a build the job finished is left alone, and the sweep still catches one whose job's end was never heard. Builds are found by an index on their job. The Deployments guide says so, with the message in its troubleshooting table.20b74aeHistory
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml