cutip v2.19.0
·
9 commits
to integration
since this release
cutip v2.19.0
What's new
cutip projects — discover all cutip projects under cwd
A new CLI verb for monorepos that host many cutip projects scattered across subdirectories. Walks the current directory tree, finds every YAML with project: + host: keys, and prints a table of (path, project name, host, description).
$ cd my-monorepo/
$ cutip projects
cutip projects under my-monorepo/
╭─────────────────────┬─────────────────┬─────────┬────────────────╮
│ path │ project │ host │ description │
├─────────────────────┼─────────────────┼─────────┼────────────────┤
│ misc/wsl/dns.yaml │ wsl-dns │ local │ Restore WSL... │
│ workspaces/api.yaml │ api │ container │ Run API... │
│ workspaces/web.yaml │ web │ local │ Build static..│
╰─────────────────────┴─────────────────┴─────────┴────────────────╯
3 projects
Implementation notes:
- Skips standard build/hidden dirs (
.git,node_modules,.venv,__pycache__,target,dist,site,.cutip,.tox,.mypy_cache,.pytest_cache) - Skips cutip artifact YAMLs (
apiVersion: cutip/v1) — those are a different schema, not project files - Description = first prose comment line scanned across the first 30 lines (ruler comments like
─────skipped) --jsonfor machine consumption- Host column color-coded: green = local, yellow = container, magenta = remote
Why
Existing inspection verbs (cutip tree, cutip show, cutip group ls) all operate on a single named project. There was no way to ask "what cutip projects exist in this tree?" without grepping for project: and decoding the results by hand. cutip projects closes that gap.
Upgrade
pip install cutip==2.19.0 --upgradeNo breaking changes from 2.18.x.