syntaqxThe CLI has g1t workflow: list shows the workflows in .g1t/workflows that are on (--all for those turned off) with their triggers and ids; view shows one with its state, triggers, manual-run inputs, notes and latest five runs, --yaml prints its file on the default branch or on --ref, and --web opens it; run runs a workflow_dispatch workflow on --ref with inputs from -f and -F (@FILE reads a file) or, with a bare --json, a JSON object on stdin, asks for each input at a terminal when none are given, and prints the run's address, looking for the run for a few seconds if the answer does not carry it; enable and disable turn one on and off. A workflow is named by its file name, id or name; left out, g1t asks at a terminal and otherwise exits 2 naming what to pass, and a name that matches none exits 1. The CLI guide has a Workflows section, the Actions guide points to it, and the command reference is regenerated.3077a27History
- ..
- deploy
- emoji
- ops
- perf
- build-runner.mjs
- build-rust-worker.mjs
- cli-release.mjs
- cli-release.test.mjs
- cloudflare-setup.py
- conformance-diff.mjs
- deploy.mjs
- deploy.sh
- desktop-release.mjs
- desktop-release.test.mjs
- mobile-release.mjs
- mobile-release.test.mjs
- runner-release.mjs
- runner-release.test.mjs
- sandbox-image.mjs
- sccache.sh
- setup-custom-domains.sh
- setup-deployments.sh