Skip to content

ci: add workflow_dispatch so CI can be run on demand #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AdaWorldAPI merged 1 commit into from
Aug 27, 2026
+7 −0
Merged

ci: add workflow_dispatch so CI can be run on demand #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading