Remove OSSF scorecard workflow #19
Merged
Conversation
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
Scorecard is now part of the test workflow. (it's in the same spirit as testing/linting/auditing) We don't bother running on the branch-protection event, though because how often is that even happening. And the recurring cron schedule would run often enough to update the relevant scorecard metric. (and on top of the frequency of the runs, the corresponding metrics are so nearly insignificant that (in)frequency of re-checking is no big deal)
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.
Scorecard is now part of the test workflow. (it's in the same spirit as
testing/linting/auditing)
We don't bother running on the branch-protection event, though because
how often is that even a thing :D . And the recurring cron schedule would
run often enough to update the relevant scorecard metric. (and on top of
the frequency of the runs, the corresponding metrics are so nearly
insignificant that (in)frequency of re-checking is no big deal)