syntaqxThe CLI coordinates work: g1t session start, heartbeat, log, attach, end, list and view record a harness's run, with the current session kept per working copy in the worktree's own git directory (g1t/session) and G1T_SESSION overriding it; g1t work context, claim, release, handoff, list, block and unblock read an issue's work and say who is on it, a claim carrying the current session; g1t work events lists the repository's events and with --follow keeps printing them, one line or one JSON object each, by holding list_events with after and wait, resuming from the last event and backing off on failures; g1t why PATH[:LINE] says which commit, pull request, issue, decisions and sessions explain a line; and g1t status lists your active sessions and claims in the current repository. These commands never prompt, fail at once with exit code 4 without a token, give up on a call after 15 seconds, and say when the server is older than the CLI. Operations the API's document does not describe yet are listed as pending in ops.rs until it does. The CLI guide and the generated command reference cover them.f867867History
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