syntaqxThe docs have a guide to the g1t CLI and a reference of every command. The guide, The g1t CLI under Get started, covers installing it, signing in (in the browser, with a token, G1T_TOKEN, self-hosted hosts), using it as git's credential helper, which repository a command works on, issues, pull requests, checks and runs, deployments, logs and secrets, scripting with --json and --jq, the exit codes, calling any operation with g1t api, and using it from Claude Code, Codex or Cursor, with lines to put in CLAUDE.md or AGENTS.md. CLI commands, under Reference, is written from the CLI's own command tree, with each command's arguments, flags and the API operations it calls, linked to their reference pages; a test fails when it falls behind (G1T_WRITE_DOCS=1 cargo test -p g1t cli_reference). Container images now says g1t push takes the token g1t auth login signed in with, and points to the guide for installing.15462a1History
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.