Add a pipeline to pull the OSSF Scorecard visualizer #901
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.
Motivation
We want to host the official Scorecard Visualizer under the official Scorecard domain. This PR enables the existing Scorecard Viewer and the Visualizer to coexist in the same space while we plan the next steps (unification, deprecation, redirects, etc.).
Main Changes
OSSF Scorecard Visualizer, builds it, and opens a PR updating the
staticfolder.https://scorecard.dev/scorecard-visualizer/#/projects/github.com/ossf/scorecard-visualizer
https://deploy-preview-902--ossf-scorecard.netlify.app/scorecard-visualizer/#/projects/github.com/ossf/scorecard-visualizer
https://ossf.github.io/scorecard-visualizer/#/projects/github.com/ossf/scorecard-visualizer
A sample of an auto-generated update PR can be seen here (from my fork):
UlisesGascon#5
Screenshots
How the Update Process Works
A scheduled GitHub Action checks daily (and can be run manually) to detect if the Visualizer project has new changes.
.last_commit.ossf/scorecard-visualizer@mainas we don't do releasesscorecards-site/static/scorecard-visualizer/.last_commitfile is updateddeps/upgrade-visualizerPR Behavior
The workflow safely handles all scenarios:
✅ PR already open
deps/upgrade-visualizerbranch is updated (force-with-lease)✅ PR merged
✅ PR closed without merging
❗ No changes detected
Note: In the PR decription we have this information:
Context