Use shared-config's reusable zizmor workflow - #121
Merged
Merged
Conversation
Replaces the copy of the zizmor workflow with a caller of rubyatscale/shared-config/.github/workflows/zizmor.yml@main (rubyatscale/shared-config#32), so zizmor-action bumps and fixes land once in shared-config instead of in every repo. It keeps the default advanced-security: true, so results still upload to the Security tab and the same triggers apply. The job no longer requests actions: read, which upload-sarif only needs in private repos. The check is now named "zizmor / zizmor"; no ruleset requires the old name.
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.
Summary
Replaces this repo's copy of the zizmor workflow with a caller of
rubyatscale/shared-config/.github/workflows/zizmor.yml@main(rubyatscale/shared-config#32). zizmor-action bumps and fixes now land once in shared-config instead of in every repo, the same way #116 did for CodeQL.advanced-security: truestill uploads results to the Security tab, with the same triggers.contents: readandsecurity-events: write. It dropsactions: read, which upload-sarif only needs in private repos.zizmor / zizmor. No ruleset or branch protection requires the oldzizmorname.Test plan
zizmor / zizmorruns on this PR and uploads to code scanning.