ci: let CI, web CI and the secret scan be triggered on demand - #117
Merged
Merged
Conversation
Follows the same change made to CodeQL in #116, for the same reason: every trigger on these waits on an event, so none of them can be asked a question. web-ci needed it most. Its paths filter is ['web/**', its own file], which is correct — a backend-only change has no reason to rebuild the SPA — but it also means the workflow can go unexercised for long stretches, and it was the one workflow still absent from the Actions registry because nothing had triggered it. The other two recovered on their own once a pull request ran them. The secret scan gains the ability to rescan history after a rule change in .gitleaks.toml without waiting for the next push to main. Deliberately unchanged: dependency-review stays pull_request-only. The action diffs a base against a head, so a manual run would have nothing to compare — its own header says so. keep-warm stays disabled_manually. That is a deployment decision about a free tier, not a registration problem, and is not mine to reverse. No paths filters on any of the manual triggers: pressing the button is an explicit request to run the whole thing. Co-Authored-By: Claude Opus 5 <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.
Extends the change made to CodeQL in #116 to the three other workflows that can meaningfully run standalone. Adds
workflow_dispatchtoci.yml,web-ci.ymlandsecret-scan.yml— a Run workflow button each, nothing else altered.Why
Every trigger on these waits on an event — a push to
mainor a pull request — so none of them can be asked a question. That mattered when the Actions registry was listing only 6 of the 11 workflows committed onmain.Three of the five missing ones (
ci,dependency-review,secret-scan) re-registered on their own once #116's checks ran them.web-cidid not, and wouldn't have: itspathsfilter is['web/**', '.github/workflows/web-ci.yml'], so a backend-only change never triggers it. That filter is correct — there's no reason to rebuild the SPA for a C# change — but it means the workflow can sit unexercised indefinitely with nothing reporting that fact. This PR touches the file, which registers it, and gives it a trigger that doesn't depend on someone happening to editweb/.The secret scan also gains something real: history can be rescanned after a rule change in
.gitleaks.tomlwithout waiting for the next push tomain.Deliberately unchanged
dependency-review.ymlstayspull_request-only. The action diffs a base against a head, so there is nothing for it to compare on a dispatch. Its own header documents this. Adding a button there would only produce runs that can't do their job.keep-warm.ymlstaysdisabled_manually. That's a deployment decision about holding a free-tier instance loaded, not a registration fault, and it isn't mine to reverse.Note on the triggers
No
paths-ignoreorpathsfilters on any of the manual triggers, matching #116. Pressing the button is an explicit request to run the whole thing, not to have it skipped because the last commit touched a markdown file.🤖 Generated with Claude Code