Repository navigation
Call the Scorecard publish check after this repository's own Scorecard runs - #200
Merged
Merged
Conversation
…d runs scorecard-publish.yml runs actions/scorecard-publish-check, pinned at the commit that added it, on workflow_run of scorecard.yml. It is the action's first caller, so the first Scorecard run on main after this merges is its first run on a runner against the real scorecard.dev.
askalf
marked this pull request as ready for review
November 10, 2026 03:02
askalf
enabled auto-merge (squash)
November 10, 2026 03:05
sprayberry-redline
approved these changes
Nov 10, 2026
sprayberry-redline
left a comment
sprayberry-redline
left a comment
Collaborator
There was a problem hiding this comment.
Verdict: approve. The new workflow calls the pinned publish check after successful Scorecard runs in public repositories, with the Actions permission needed for its bounded retry. Its trigger matches the existing Scorecard workflow, and the README and changelog identify the new caller accurately.
This was referenced Nov 10, 2026
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
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 changes, and why
#199 added
actions/scorecard-publish-checkand left it with no caller, since a caller pins a commit ofmainthat has it. This adds this repository's own:.github/workflows/scorecard-publish.yml, the workflow the README shows, pinned at50ee9df(the merge of #199).It runs on
workflow_runofScorecard, only for a run that succeeded and only while the repository is public, on a GitHub-hosted runner, withactions: writeon the job and no other permission. The README's list of this repository's own workflows and the changelog entry name it.A
workflow_runworkflow runs from the default branch's copy, so nothing here runs on this pull request. The push tomainthat merges it starts a Scorecard run, and that run's completion is the action's first run on a runner against the real scorecard.dev. It settles the two things #199 said it relies on: that the runner fills the action's input defaults fromgithub.event.*(if not, the check fails on a missing run id), and, should a publish fail, that a run dispatched with the job token is checked in turn.How it is tested:
node test-all.mjspasses (all 12).actionlint1.7.12 reports nothing on the new file, andpin.mjs --action-pinsreads its pin, so the pin bump will move it.Callers: no. The file is this repository's own workflow and is outside the paths the pin bump watches.