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
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