2 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 4.8	fcbd1072b6	fix(lint): check fmt.Fprintf errors in webhook handler (infra#190) ... errcheck flagged two unchecked fmt.Fprintf return values in internal/webhook/webhook.go, failing CI (run 310/311) for the whole 'trigger brain-sync on Gitea push' feature -- so no new ingestion image was ever built, and the deployed image predates this feature entirely even though infra's manifest (secret, RBAC, env wiring) was already live. Both writes are best-effort informational text after WriteHeader has already committed the status code -- a failed write here only happens on client disconnect and nothing depends on it succeeding, so explicitly discard (_, _ =) rather than log-and-continue noise. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-09 08:29:39 +02:00
mathias	394a227877	feat(webhook): trigger brain-sync on Gitea push instead of 15-min poll ... Adds POST /webhooks/brain-sync: verifies Gitea's HMAC-SHA256 signature, checks the push is to mathias/brain main, then creates a one-off Job from the existing brain-sync CronJob's template (same script the 15-min poll already runs, just triggered on-demand). Off by default -- opt in via GITEA_WEBHOOK_SECRET, since it needs Job-create RBAC in the "brain" namespace a fresh deploy won't have. 10 new tests (internal/webhook), including a fake-clientset reactor to simulate server-side GenerateName expansion, which the plain fake tracker doesn't do on its own. Needs (follow-up, infra repo): RBAC granting ingestion's ServiceAccount get on cronjobs/brain-sync + create on jobs in the brain namespace, the GITEA_WEBHOOK_SECRET env, and the actual Gitea webhook registration.	2026-07-07 22:00:56 +02:00