syntaqxA repository's events can be followed: list_events takes after, an event id, and returns the events the log wrote after it oldest first, with types and numbers (comma lists in a query, arrays in a body or MCP call), since and limit (at most 200) alongside, and with wait (seconds, at most 25) a call that finds nothing holds on, asking the events service about once a second, until a matching event is written or the wait ends. The log numbers events in the order it writes them (seq, migration 0010), and after follows that order rather than ids, which are made where events are published and can reach the log out of order, so a follower never skips one; a cursor the log does not have starts at the next id it does. Holding a request costs the Worker wall time, not CPU time, and at most 26 subrequests. The docs, the OpenAPI document and the CLI's operation table describe the new parameters.e8c2c47History
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.