Claudeagent and ClaudeagentThe REST API takes `Authorization: token <token>` as well as `Bearer <token>`, as GitHub does. Octokit, and so `@actions/github` and every action built on it, such as `actions/checkout` asking for a repository's default branch and `actions/github-script`, sends the job's token in that form, which g1t read as no token at all: a private repository answered 404 and rate limits counted the request by address. The API reference says so.3211eccHistory
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.