Mike Swanson
c67accddcc
Host guard in /opt/gururmm/webhook-handler.py skips docs-only pushes; note the stale repo copy must not be redeployed over it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.3 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| project_rmm_webhook_docs_guard | RMM build webhook now skips docs-only pushes (host guard in /opt/gururmm/webhook-handler.py). The repo copy is stale — don't redeploy it. |
|
The GuruRMM build webhook (gururmm-webhook.service → /opt/gururmm/webhook-handler.py
on 172.16.3.30) has a docs-only build guard as of 2026-05-30: a push whose every
changed file matches docs/, *.md, .claude/, session-logs/, LICENSE, or
.gitignore returns Docs-only change -- build skipped and triggers no build.
Fail-safe toward building — no file list or any buildable file → build runs. Detection
uses the Gitea push payload's per-commit added/removed/modified lists
(is_docs_only / NON_BUILDABLE). Verified live (docs push skipped, no build locks,
last-built-commit unchanged). Backup: /opt/gururmm/webhook-handler.py.bak-20260530-guard.
This is SPEC-020 Phase 0 (interim). The full fix migrates RMM CI to Gitea Actions
with native paths-ignore, matching GuruConnect (ADR-002) — see reference_gitea_internal.
Caveat: the repo copy scripts/webhook-handler.py is STALE (109 lines vs the deployed
206 — predates the split-build refactor) and does NOT contain the guard. Do not redeploy
it over the host copy; the host is the source of truth until SPEC-020 lands.