Add lint + reload-trigger workflow

Validates YAML/required fields/duplicate ids/requirement types with yq+jq against the exact shape content.rs parses (not a full schema check - that would mean building portal just to lint content), then publishes portal.content.reload over NATS so every running portal instance picks up the change without a restart (portal's own content::watch_for_reload, added alongside this).
2026-08-05 07:19:07 +02:00
parent d8628dbd15
commit fc4cd1b86e
2 changed files with 85 additions and 0 deletions
@@ -0,0 +1,21 @@
+name: Lint and reload
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  lint-and-reload:
+    runs-on: bare
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Lint questions
+        run: ./lint.sh questions
+
+      # Tells every running portal instance to re-fetch and atomically
+      # swap in the new content - see content::watch_for_reload in the
+      # portal repo. Fire and forget: no reply expected, no payload
+      # needed (the subject alone is the whole message).
+      - name: Tell portal to reload content
+        run: nats pub portal.content.reload '' --server "nats://infra:${{ secrets.NATS_TOKEN }}@127.0.0.1:4222"