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
GitHub's workflow schema
workflow-v1.0.json is GitHub's schema for workflow files, copied unchanged from
actions/languageservices, file
workflow-parser/src/workflow-v1.0.json, at commit
4043eda158e16579cc5fb1b0b07a4bce2a76f0b5 (5 August 2026). It is MIT licensed;
LICENSE is that repository's licence, copied from the same commit.
g1t does not read it at run time. src/syntax.rs lists the keys each part of a
workflow may have, and its tests check those lists against this file, so they
cannot drift from GitHub's. To update it, copy the file again, write the commit
here, and run cargo test -p g1t-actions.