syntaqxThe merge queue works out who answers for a failed combination and tells the work: a state that fails while an entry ahead of it is still being tested is held until those ahead settle, so a broken change is blamed on itself and the entries tested with it are tested again instead of being taken out; an entry whose own checks pass but which fails with several entries ahead has smaller combinations (the default branch, half of the suspects and the entry) built and checked by the merge_group workflows, halving the suspects within three extra builds, and never landed. The result goes on the pull request's and its issue's timelines and into its session, as an integration_failure decision record (tested), and as integration.failed with the pull request, its issue, the combination, the failing check's name, conclusion and link, whether it was bisected, the suspects and the other pull requests; a combination that passes is an integration_passed decision and integration.passed. An entry the queue took out keeps its merge request: once a new commit's checks all pass, g1t merges it again as whoever queued it, which puts it back in the queue under the branch's rules as they are then.c9e737fHistory
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.