ci: allow CI to be dispatched against a ref - #36
Merged
Merged
Conversation
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) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prerequisite for fixing the spec-drift PRs, and inert on its own.
Adds
workflow_dispatchto the CI workflow.pushandpull_requeststill trigger it exactly as before; this only makes the workflow startable against a chosen ref.Why it is needed: the drift job opens its PR with
GITHUB_TOKEN, and GitHub does not start workflow runs fromGITHUB_TOKEN-raised events. The requiredTest (Node …)checks therefore never report, and #34 sits blocked on a report it can never receive.workflow_dispatchandrepository_dispatchare the two documented exceptions, so drift can start its own CI run.A workflow has to carry the trigger on the default branch before it can be dispatched at all, which is why this lands first and separately. The drift-job change follows once the mechanism is proven end to end.
🤖 Generated with Claude Code