From bf506a83f2128b8a70c8abc5c01ca6a297f8f4c8 Mon Sep 17 00:00:00 2001 From: Bendik Aagaard Lynghaug Date: Wed, 12 Aug 2026 22:21:27 +0200 Subject: [PATCH] CI: lint on pull requests too, reload only on pushes to main 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 --- .gitea/workflows/lint-and-reload.yml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/lint-and-reload.yml b/.gitea/workflows/lint-and-reload.yml index 831491a..07f03fc 100644 --- a/.gitea/workflows/lint-and-reload.yml +++ b/.gitea/workflows/lint-and-reload.yml @@ -1,11 +1,16 @@ name: Lint and reload +# Lint runs on PRs too - it's the status check branch protection +# requires before the development-commit automation's PRs may merge +# (merge_when_checks_succeed). The reload only ever fires on a push +# that actually landed on main. on: push: branches: [main] + pull_request: jobs: - lint-and-reload: + lint: runs-on: bare steps: - uses: actions/checkout@v4 @@ -18,6 +23,11 @@ jobs: - name: Lint questions run: /srv/app/uhhm-portal/current/question_lint --path questions + reload: + runs-on: bare + needs: lint + if: github.event_name == 'push' + steps: # 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