CHAPTER ZERO · ABSTRACT
ticgit is a distributed issue system that stores tickets as metadata using the git meta toolkit. it does not run a server. it does not require a proprietary web application. it does not have downtime. it synchronises issue data using the same protocol you already use to move source code.
§ 4.0 — FIELD MANUAL PROCEDURES
`ti agent` to learn ticgit, then find the
next ticket, fix it and close it
TicGit publishes a stable JSON schema for agent and automation
workflows. Use it when parsing ti show --json, JSON
mutation output, or ti list --json.
Download schema v1 or read the agent-friendly Markdown site at docs/index.md.
ti show --json emits a ticket object.
ti list --json emits an array of ticket objects. Ticket
metadata appears under .meta as string values.
Tickets include status (open or
closed) and state. Open states are
new, assigned, in-progress,
blocked, and review. Closed states are
resolved, wontfix, duplicate,
and invalid.
--json is the stable machine interface: successful
commands write parseable JSON to stdout only, diagnostics go to
stderr, JSON output has no ANSI color escapes, and failures return a
non-zero exit status.
Ticket ids may be full UUIDs or unique UUID prefixes. Ambiguous or missing prefixes fail with a stderr diagnostic.
--porcelain and --format json are not
supported compatibility aliases today; use --json.