Glossary
The words qq uses, defined once.
The guides link here instead of defining terms again.
| Term | What it means |
|---|---|
quirq's build and release infrastructure, and its command line, qq. | |
infra/repo.toml | The one file a repo writes to use qq: its targets, the toolchains they need, and its qq version. Read only through qqsync. Also called the manifest. |
| Target | One thing a repo builds or tests, with a name and a kind. |
| Kind | The type of a target, such as node-app or pytest. It decides the steps. Kinds are defined once for the org in infra-config, and given their steps by recipes. |
| Toolchain | The Python, or Node with pnpm, that a build uses. |
| Pinned by digest | Named by the hash of its exact bytes, so every machine that fetches it gets the same bytes. Not a version number. |
| infra-config | The repo that holds every policy as TOML. Not a repo's own infra/repo.toml. |
| gate | The repo that applies required checks, repo settings and the merge queue. |
| Presubmit | The required check on a pull request, named <repo>-presubmit. |
| Merge queue | GitHub's queue that tests each pull request on top of the latest main, and the ones ahead of it, before it lands. |
| Verdict | The gate's answer for a change: pass, refused or pending. qq status prints it. |
| Post-submit | The build that runs on each main commit after a change lands. |
| Tree status | Whether a repo's main is green: open, closed or unknown. Published by gardener. |
| lkgr (last known good) | The newest main commit whose post-submit builds all passed. Not the canary. |
| Channel | A pointer to a commit and the digest of what was built from it: canary now, dev and stable later. |
| Canary | The daily channel. Once a day lkgr is built, tested, started and probed, then the canary moves to it. |
| Roll | A pull request that moves a pin forward: a dependency version or a toolchain digest. |
| v0, v1, v2 | qq's three versions. v0, the first thin version, is being finished now. See the roadmap. |