Workflows
Workflows in .g1t/workflows, written as GitHub Actions and run as GitHub runs them. A run on a pull request counts as its checks.
How this runs on g1t · 8 notes
- build: `actions/checkout` checks out from g1t.
- build: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- build: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- build: `actions/upload-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- publish: `actions/checkout` checks out from g1t.
- publish: `actions/download-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- publish: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- publish: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
- CLI release run by syntaqx#7 · manual by syntaqxcli-v0.3.69m 53s
- CLI release run by syntaqx#6 · manual by syntaqxcli-v0.3.58m 50s
- Merge remote-tracking branch 'g1t/main' into ship-42-43#5 · push by syntaqxcli-v0.3.412m 26s
- The g1t CLI is 0.3.3: any harness reads and acknowledges its coordination updates. `g1t session updates [ID]` lists what other sessions did that concerns this one (claims, overlaps, dependency changes, decisions, merge queue results), which reading never clears; `g1t session acknowledge ID... --note TEXT` records the decision about them and clears exactly those IDs for this session (`--session` names another of yours), and says when an ID was not this session's. `session updates`, `acknowledge` and `heartbeat` first say which files the working copy changed (git status), so another session changing the same files is an overlap.detected for both, whatever harness either runs in (G1T_TOUCH=0 turns it off). The CLI guide lists both commands. Checked: cargo test -p g1t (105 and 44, the command reference current).#4 · push by syntaqxcli-v0.3.37m 53s
- The README says what g1t is now and only what works today: g1t is the git platform people's own coding agents work through (Git tracks changes, g1t coordinates change), with sessions, Live now, claims, integration in the merge queue, why-blame, memory and Ask first, then Code, Deployments and observability, the workspace and how to extend it. Gone are the hosted agents, templates, skills, Customize, the Marketplace, invite-only sign-up, assigning an issue to g1t and every Coming row, none of which g1t offers. Try it installs the CLI and the Claude Code plugin; the layout drops the agents, models and context services, which are no longer deployed, and adds telemetry, the desktop and phone apps and the plugins; running your own says deployments and billing are off rather than agents. Checked: every g1t command in it against the CLI (cargo test -p g1t).#3 · push by syntaqxcli-v0.3.27m 43s
- The g1t CLI is 0.3.1, with g1t workflow (list, view, run, enable, disable) and g1t cache (list, usage, delete).#2 · push by syntaqxcli-v0.3.111m 21s
- Merge branch 'worktree-agent-aa68cf6ecc03dffaf'#1 (attempt 3) · push by syntaqxcli-v0.3.02m 19s