id: pipelines title: CI runs, and its runs are readable from here status: open repos: [atgc] dependsOn: [] exitCriterion: > This repo's workflow has run on a spindle, and atgc run reads runs and logs back. #

pipelines #

.tangled/workflows/ci.yml exists and no runner has ever executed it, so its schema is unproven and so is the assumption that the nixpkgs toolchain agrees with rust-toolchain.toml's pin about fmt and clippy.

Attaching a spindle is the gate for three other things: the integration suite has never run anywhere but a developer's machine, artifacts needs somewhere to build a binary, and secrets has nothing to be a secret for. It is deliberately part of the 1.0.0 arc rather than a step on the way to it — see publishing.

What it needs #

• Attach a spindle to this repo. .tangled/workflows/ci.yml exists but is unverified — no runner has ever executed it, so its schema is unproven. It also assumes the nixpkgs cargo/rustc attrs resolve, and that the nixpkgs toolchain is close enough to rust-toolchain.toml's pin that fmt and clippy agree with a local run. Deferred to the 1.0.0 arc under Infrastructure, alongside crates.io publishing and release binaries
• run list / run view — pipeline runs and workflow logs over spindle XRPC (v1.16+)
• run watch — poll a run until it completes
• run rerun / run cancel — spindle retry/cancel (rpc:sh.tangled.ci.triggerPipeline / cancelPipeline)
• run trigger — kick off a workflow manually
• pr checks — pipeline status for the PR's latest round
• No spindle is attached, so the integration suite has never run anywhere but a developer's machine. It needs only a Rust toolchain, git and loopback — no secrets, no network — so it should go green on the first CI run that happens. Until one does, that is unproven

Done #

• Clear the pre-existing cargo fmt --check and clippy findings so the pipeline's fmt and -D warnings gates can go green (prek run --all-files is clean; the pipeline itself still hasn't run once)