From dee08220a62c607f330cd031045642535445ae2e Mon Sep 17 00:00:00 2001 From: Phil Leggetter Date: Tue, 15 Sep 2026 00:36:01 +0100 Subject: [PATCH] ci: allow the acceptance suite to be run on demand The pull_request trigger does not fire when a PR's head branch is updated by merging another PR into it. Merging #392 into the v2.6.0 release branch moved it 20 commits and 75 files, and produced no acceptance run at all -- so the code about to ship had never been through the gate it is judged by. There was no way to force one: this workflow had no manual trigger, and re-running an existing run re-runs the commit it was created for, which says nothing about the new code. workflow_dispatch closes that. Note GitHub reads the workflow definition from the ref being dispatched, so a branch can only be dispatched once it also carries this block -- merging it to main is necessary but not sufficient for an existing release branch. Related: #395 (CI does not run on PRs that target a branch other than main). Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01BnrKWZQASV7bFJ4oGWwmo9 --- .github/workflows/test-acceptance.yml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/workflows/test-acceptance.yml b/.github/workflows/test-acceptance.yml index 68a5186d..2866448c 100644 --- a/.github/workflows/test-acceptance.yml +++ b/.github/workflows/test-acceptance.yml @@ -5,6 +5,16 @@ on: branches: - next - main + # Allow running the acceptance suite against any branch by hand. + # + # The pull_request trigger above does not fire when a PR's head branch is + # updated by merging another PR into it, so a stacked release branch can end + # up with no acceptance run at all. workflow_dispatch is the only way to + # exercise that code before it reaches main. + # + # Note GitHub takes the workflow definition from the ref you dispatch, so a + # branch can only be dispatched once it also carries this block. + workflow_dispatch: {} jobs: acceptance: