Cancels superseded PR CI runs on a new push, never during a live deploy

A new push to a PR previously left the prior CI attempt running independently instead of superseding it. Scoped strictly to pull_request events, since deploy-test/deploy-production only ever run on a push to master or a manual workflow_dispatch. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FWyStNL2ZsjrS7FLd7xvvN
2026-08-02 16:37:58 +02:00
parent 81af6cd151
commit c43528b7b2
2 changed files with 21 additions and 0 deletions
@@ -935,3 +935,15 @@
 **Context**: Operations, Production Readiness Validation stage complete — the final stage of this feature's AI-DLC lifecycle. Presenting the feature-completion gate; awaiting the user's final approval to close out `slpsoftware-api`.

 ---
+
+## Post-Completion Q&A — CI Concurrency Cancellation
+
+**Timestamp**: 2026-08-02T17:50:00Z
+
+**User Input**: "Ja, commit alle openstaande wijzigingen. Is het trouwens mogelijk een workflow run te stoppen als er een nieuwe push wordt gedaan naar de pull request of zou dat al moeten gebeuren?" — followed by "Ja, voeg maar toe" after being told this isn't automatic and being shown the fix.
+
+**AI Response**: "Committed the Operations-phase doc changes (commit `81af6cd`, not pushed). Answered the concurrency question: confirmed via the Gitea server's `/api/v1/version` (1.27.0, well past when Gitea Actions gained `concurrency:` support) that neither Gitea nor GitHub Actions cancels a previous run on a new PR push by default — each `synchronize` event starts an independent run. Added a workflow-level `concurrency` block to `continuous_integration.yaml`, scoped to only cancel on `pull_request` events (`cancel-in-progress: ${{ github.event_name == 'pull_request' }}`) — verified `deploy-test`/`deploy-production`'s existing `if:` conditions never trigger on a `pull_request` event (only push-to-master or `workflow_dispatch`), so this can never abort a live deploy mid-flight."
+
+**Context**: Post-completion CI/CD hygiene improvement, within this feature's already-established Operations-phase scope (it already owns the retargeted `continuous_integration.yaml`). Not yet committed — awaiting the user's decision on whether to fold this into a new commit or the next one.
+
+---