From b121f8aa55b6ba4bcfb9738cb72e2b545e80c6b4 Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Tue, 8 Sep 2026 18:47:19 -0500 Subject: [PATCH] CLAUDE.md: fix monitor-ci.sh doc mismatch, no --commit flag exists The script only ever took positional args ([repos] [branch] [sha_pgxntool_test] [sha_pgxntool]) - the --commit SHA flag text appears to have crept in from ../ai/CLAUDE.md's general gh CLI advice (gh run list/gh pr checks do take --commit) getting conflated with this script's own interface. An agent following the doc literally invoked `monitor-ci.sh --commit SHA`, which silently misparsed and hung until timeout polling a nonexistent branch. Companion fix in pgxntool-test#82 (monitor-ci.sh itself, plus its own SKILL.md). --- CLAUDE.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 17ca775..e865f86 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -12,9 +12,12 @@ sequentially. The CI monitor lives in the pgxntool-test checkout: run `bash ../pgxntool-test/.claude/skills/ci/scripts/monitor-ci.sh` (the `/ci` skill). It monitors both repos and derives the owner from the current repo. -Pass the exact push SHA when available — `gh run list --branch` has a race -condition: if two pushes land close together on the same branch, `--branch` -may pick up the wrong run. `--commit SHA` targets the exact push and avoids it. +Pass the exact push SHA(s) as positional arguments when available (the +script takes `[repos] [branch] [sha_pgxntool_test] [sha_pgxntool]`, not a +`--commit` flag — see the `/ci` skill for exact usage) — `gh run list +--branch` has a race condition: if two pushes land close together on the +same branch, `--branch` may pick up the wrong run. An exact SHA targets +the push directly and avoids this. ## Scope of This File