From b41677f8317b33b6a022f6fb6a6fe766da4ec98d Mon Sep 17 00:00:00 2001 From: Paul O'Reilly Date: Tue, 7 Jul 2026 17:52:19 +1200 Subject: [PATCH] CLAUDE.md: add Gitea CI visibility section pointing at gitea-agent-companion (gac --help) --- CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 9e15f8b..2473e6f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -63,6 +63,10 @@ Then proceed directly to step 2. Otherwise: - When a task requires a secret, read it at execution time from the secrets folder and use it ephemerally. Do not cache or persist the value. - Referencing the **existence** of a secret file is fine (e.g., "credentials are in `~/dev/claude/secrets/gitea/ai_enablement`") — referencing the contents is not. +## Gitea CI visibility + +When working with Gitea (watching Actions runs, checking whether a release/container built, diagnosing failing CI), use `gitea-agent-companion` — alias `gac`, installed in `~/sbin`, source at `projects/gitea-agent-companion`. Run `gitea-agent-companion --help` first: the help text is the full reference (verbs, flags, token discovery, exit codes). Canonical post-push pattern: `gac tail --until run-complete --timeout 600`; on failure, `gac inspect --run --logs`. + ## Process Principles Hard-won lessons that apply across every project: