syntaqxA file's blame is fetched by its page, so a slow first one still arrives. 834f2998 streamed blame from the blob loader, but the site keeps a page's stream open for 5 seconds (entry.server.tsx streamTimeout), and a first blame can take up to about 6 (repos' walk is cut at 6 s): live on flagon-io/g1t's services/actions/src/plan.rs at 834f2998 the stream ended at 5.7 s with the blame cut off, the browser logged Unexpected Server Error, and the page said "Working out who changed each line" for good. The page now opens with the file and fetches the blame from /<owner>/<repo>/blame/<ref>/<path> (routes/repo/blame-data.ts, JSON, private and noindex), on a request of its own with no stream to outlast; it says the blame could not be worked out when the request fails. robots.txt keeps crawlers off that path too (Disallow: /*/*/blame/). Checked: the site's typecheck (tsc -b --force) and unit tests (950 passing, the robots test with the new rule).0c83797History
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.