From 36d9c9982569b87e017d9882c1cc9d5aebcfa4c1 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 27 Aug 2026 08:38:13 +0000 Subject: [PATCH] ci: add workflow_dispatch so CI can be run on demand MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Enabling Actions on a repository does not retroactively create runs for events that already happened, and this workflow had no manual trigger — so after the Actions setting was turned on there was no way to prove it worked short of waiting for the next push. workflow_dispatch is also the honest way to re-run after provisioning a self-hosted runner or installing libz3, instead of pushing an empty commit to kick CI. --- .github/workflows/ci.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index bb7cdc15..46803d41 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -5,6 +5,13 @@ on: branches: [master] pull_request: branches: [master] + # Manual trigger. Needed in practice, not decoration: enabling Actions on + # a repository does NOT retroactively create runs for events that already + # happened, so without this the only way to prove a newly-enabled (or + # newly-provisioned) runner works is to wait for the next push. It is also + # the honest way to re-run after a runner is registered or libz3 is + # installed, rather than pushing an empty commit to kick CI. + workflow_dispatch: # Cancel in-progress runs for the same branch/PR concurrency: