-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(zizmor): add a reusable workflow for zizmor GitHub Actions static analysis #605
Open
iainlane
wants to merge
2
commits into
main
Choose a base branch
from
iainlane/add-zizmor-reusable-workflow
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
This comment has been minimized.
This comment has been minimized.
iainlane
force-pushed
the
iainlane/add-zizmor-reusable-workflow
branch
6 times, most recently
from
December 2, 2024 14:24
2f972d2
to
9488aad
Compare
…c analysis This is a [reusable workflow] which runs the [`zizmor`][zizmor] static analysis tool on a repo's GitHub Actions workflow files. This will report things such as whether there is potential for untrusted code to be injected via a template. See a full list of checks in [the documentation][zizmor-checks]. This workflow will run zizmor, upload results to GitHub's code scanning service (requires an Advanced Security subscription for private repositories), and comment on the pull request with the results. The comment will be re-posted on each run - and previous comments hidden - so the most recent comment will always show the current results. [reusable workflow]: https://docs.github.com/en/actions/using-workflows/reusing-workflows [zizmor]: https://woodruffw.github.io/zizmor/ [zizmor-checks]: https://woodruffw.github.io/zizmor/audits/
iainlane
force-pushed
the
iainlane/add-zizmor-reusable-workflow
branch
from
December 2, 2024 14:28
9488aad
to
94890b3
Compare
This comment has been minimized.
This comment has been minimized.
In this PR I introduced and fixed some problems that the script found. You can see that above 👍 If you look at the files changed tab, you can see results for the other files (same as in the comment) |
zerok
approved these changes
Dec 2, 2024
iainlane
commented
Dec 3, 2024
😢 zizmor failed with exit code 14. Expand for full output
|
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.
This is a reusable workflow which runs the
zizmor
static analysis tool on a repo's GitHub Actions workflow files. This will report things such as whether there is potential for untrusted code to be injected via a template. See a full list of checks in the documentation.This workflow will run zizmor, upload results to GitHub's code scanning service (requires an Advanced Security subscription for private repositories), and comment on the pull request with the results. The comment will be re-posted on each run - and previous comments hidden - so the most recent comment will always show the current results.