ci: add workflow_dispatch trigger to OpenSSF Scorecard workflow#114
Merged
Conversation
Lets the Scorecard scan be re-run on demand (gh workflow run scorecard.yml or the Actions UI) instead of waiting for the next push to main or the weekly cron. Useful for refreshing the published score after a posture change or once the repo ages past a time-based check such as Maintained, which scores 0 for repos younger than 90 days.
🏗️ CDK infra diff — PR vs
|
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.
What
Adds a
workflow_dispatch:trigger to.github/workflows/scorecard.yml.Why
The Scorecard scan previously only ran on push to
main, weekly cron (Mon 09:45 UTC), and branch-protection changes — with no way to trigger it on demand. That matters for time-based checks: the Maintained check scores 0 for repos younger than 90 days, so after the repo crosses 90 days the published score stays stale until the next scheduled scan (andGITHUB_TOKEN-driven auto-merges tomaindon't cascade into thepushworkflow, so PR merges don't refresh it either).With this, the scan can be re-run anytime via
gh workflow run scorecard.ymlor the Actions UI.Scope
CI workflow YAML only — no Python, infrastructure, dependency, or API-surface changes. Validated with the file-scoped pre-commit hooks (
check-yamlet al. pass); the code-surface gates (tests, cdk-synth, OpenAPI, lockfile) are not applicable.