uhhm/questions
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
42 Commits 1 Branch 0 Tags
f25dedd7427a60a40b9deb23e016ed6ab7174b71
Commit Graph
8 Commits
Author SHA1 Message Date
Bendik Aagaard LynghaugandClaude Fable 5 f25dedd742 Pin portal v0.2.1 - asset cache revalidation, stable title on nav
Deploy instance / deploy (push) Successful in 0s
Details
Lint and reload / lint (push) Successful in 2s
Details
Lint and reload / reload (push) Successful in 1s
Details 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-24 22:43:14 +02:00
Bendik Aagaard LynghaugandClaude Fable 5 f243494499 Pin portal v0.2.0; document tree routing in the schema reference
Deploy instance / deploy (push) Successful in 1s
Details
Lint and reload / lint (push) Successful in 2s
Details
Lint and reload / reload (push) Successful in 0s
Details 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-24 22:33:16 +02:00
Bendik Aagaard LynghaugandClaude Fable 5 380593a998 Pin portal v0.1.0 - first semver release
Deploy instance / deploy (push) Successful in 1s
Details
Lint and reload / lint (push) Successful in 2s
Details
Lint and reload / reload (push) Successful in 0s
Details 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-08-24 21:45:45 +02:00
Bendik Aagaard Lynghaug bb117c1a1b Amend: GITEA_ is a reserved Actions secret-name prefix
Deploy instance / deploy (push) Successful in 1s
Details
Lint and reload / lint (push) Successful in 3s
Details
Lint and reload / reload (push) Successful in 0s
Details
2026-08-24 21:26:26 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5 bf506a83f2 CI: lint on pull requests too, reload only on pushes to main
Lint and reload / lint (push) Successful in 2s
Details
Lint and reload / reload (push) Successful in 0s
Details 
A development-proposal PR previously got no check at all (the workflow
only fired on push to main) - so branch protection's required status
check, the thing that makes the automation's merge_when_checks_succeed
an actual lint gate, had nothing to require. Lint now runs on both
events; the content-reload NATS publish stays push-only.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-12 22:21:27 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5 bc18add801 Lint with portal's question_lint binary, not the hand-maintained yq/jq script
Lint and reload / lint-and-reload (push) Successful in 2s
Details 
lint.sh only ever checked shape (missing id/name, duplicate ids, bad
requirement types) - it never validated transition targets against the
real state machines. question_lint runs portal's actual validation
logic (content::validate_questions) with no portal build required in
this repo's CI, since portal's deploy job now publishes it to a stable
path on the same runner/host.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-11 21:16:54 +02:00
Bendik Aagaard Lynghaug 1f0d930768 Invoke lint.sh via bash - checkout didn't preserve the exec bit
Lint and reload / lint-and-reload (push) Successful in 3s
Details
2026-08-05 07:20:18 +02:00
Bendik Aagaard Lynghaug fc4cd1b86e Add lint + reload-trigger workflow
Lint and reload / lint-and-reload (push) Failing after 2s
Details 
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