From aca3e4bf73ee358b4d172c54ba32c14f5b3651a2 Mon Sep 17 00:00:00 2001 From: Jamie Holding Date: Tue, 8 Sep 2026 09:07:21 +0100 Subject: [PATCH] ci: allow CI to be dispatched against a ref Adds workflow_dispatch to the CI workflow. No behaviour change on its own: push and pull_request still trigger it exactly as before. This is the prerequisite for letting the spec-drift job start CI for its own PR. Drift opens that PR with GITHUB_TOKEN, and GitHub does not start workflow runs from GITHUB_TOKEN-raised events, so the required checks never report and the PR is permanently blocked on a report it cannot receive. workflow_dispatch and repository_dispatch are the two documented exceptions to that rule. A workflow must carry the trigger on the default branch before it can be dispatched at all, so this lands first and on its own. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/ci.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 86bb5c8..1eff46c 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -5,6 +5,14 @@ on: branches: [main, v7] pull_request: branches: [main, v7] + # Lets another workflow start this one against a specific ref. + # + # The spec-drift job opens its PR with GITHUB_TOKEN, and GitHub does not + # start workflow runs from GITHUB_TOKEN-raised events — so the required + # checks never report and the PR is blocked on a report it can never get. + # workflow_dispatch and repository_dispatch are the two documented + # exceptions to that rule, so drift can dispatch this run itself. + workflow_dispatch: jobs: test: