From 8daf73b8c3d3e0150f30e56e0579ebe46c4dc9a3 Mon Sep 17 00:00:00 2001 From: Oleks Date: Sat, 6 Jun 2026 12:51:47 +0300 Subject: [PATCH] fix line-length lint in ops.md --- agents/ops.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/agents/ops.md b/agents/ops.md index 70d5a53..f8e725c 100644 --- a/agents/ops.md +++ b/agents/ops.md @@ -36,11 +36,13 @@ is the #1 failure mode: - `nbapi summary` → counts, billable CPU-seconds, NAR output size. - `nbapi usage --from YYYY-MM-DD --to YYYY-MM-DD` → billable CPU over a range. - `nbapi builds --limit N` → recent builds (id, status, drv path, timing). - - `nbapi build ` → single build detail including `status_message` (the failure reason). + - `nbapi build ` → single build detail including `status_message` + (the failure reason). - **`nbshell '' ['' …]`** — run admin-shell commands in one session, output cleaned. Useful commands: `usage`, `settings --show`, `settings substituters --add `, `ssh-keys`, `tokens`, `builds`, - `builds log ` (full build output). (`exit` is NOT valid — the session ends on its own.) + `builds log ` (full build output — the only way to see remote logs). + (`exit` is NOT valid — the session ends on its own.) - **`nb-substituters `** — a guarded front end for cache settings that catches the path-style-URL mistake (see below) before it reaches the shell. @@ -83,6 +85,7 @@ The full log lives on nixbuild's side. To retrieve it: output, failing test, or missing dependency. Example flow: + ```bash nbapi builds --limit 5 # find the failed build id nbapi build # check status_message first