ci: guard scorecard behind SCORECARD_ENABLED repo var - #628
Conversation
…414) Adds the OSSF Scorecard workflow (same shape as jira-cli's `scorecards.yml`, see Zious11/jira-cli#628) with the analysis job opt-in from day one: it runs only when the repo variable `SCORECARD_ENABLED` is set to `true` — the same opt-in pattern already used for `SIGNING_ENABLED`. No var, no run. Forks and clones stay quiet by default; enable per repo by adding the variable. Co-authored-by: Jared Richards <jaredbrichards@gmail.com>
|
Diagnosed the two failing checks — unrelated to this PR's change (the diff is 4 lines in
Fix: update the branch against |
|
To make the fix copy-paste executable (this account can't push to this branch): no file content changes are needed — the remedy is purely a branch refresh, since the DEAD citations name files that exist on current Either click Update branch on this PR, or: git fetch origin develop ci/scorecard-guard
git checkout ci/scorecard-guard
git merge origin/develop # conflict-free — this branch touches only .github/workflows/scorecards.yml
git push origin ci/scorecard-guardVerified locally on exactly that merge: mounted |
Scorecard analysis is now opt-in: the job runs only when the repo variable SCORECARD_ENABLED is set to true (same opt-in pattern as SIGNING_ENABLED). No var, no run — forks and clones stay quiet by default.
7584b52 to
2d5ae74
Compare
Makes Scorecard analysis opt-in: the job runs only when the repo variable
SCORECARD_ENABLEDis set totrue— the same opt-in pattern already used forSIGNING_ENABLED. No var, no run. Forks and clones stay quiet by default; enable per repo by adding the variable.