-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
use zizmor to lint github action workflows
#11269
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
Merged
Merged
Changes from all commits
Commits
Show all changes
29 commits
Select commit
Hold shift + click to select a range
135056c
add `zizmor` to the hooks
keewis b43ce8a
set the default permissions to minimum
keewis 7508cac
don't persist credentials
keewis db80e00
pin `actions/checkout`
keewis f8fc5cd
pin `xarray-contrib/ci-trigger`
keewis 2c3c235
pin `actions/upload-artifact`
keewis 0da3452
pin `actions/download-artifact`
keewis 7277523
pin `pypa/gh-action-pypi-publish`
keewis 241e0e5
pin `actions/setup-python`
keewis 74f4cf8
pin `prefix-dev/setup-pixi`
keewis 53a67c8
pin `codecov/codecov-action`
keewis 708296a
pin `scientific-python/issue-from-pytest-log-action`
keewis d7330f7
pin `mamba-org/setup-micromamba`
keewis d985643
pin `WyriHaximus/github-action-get-previous-tag`
keewis 52c8586
pin `EnricoMi/publish-unit-test-result-action`
keewis 11b2aa1
pin `actions/labeler`
keewis b602b1a
pin `actions/cache`
keewis e84ac0c
actions cooldown for dependabot
keewis a8a65c8
avoid potential template injections
keewis dbbf6da
broken condition
keewis c6f6604
ignore the `pull_request_target` warning
keewis dbbb667
ignore zizmor's dangerous-triggers warning for publish-test-results
keewis 62db312
fetch the `codecov` token from a github environment
keewis 8169e83
correct the pin for `setup-pixi`
keewis 701eb5e
split the nightly wheels ci into build and publish jobs
keewis 47ba6e1
remove the codecov env and ignore the zizmor warning instead
keewis 3bf02bf
back to the codecov env, but disable deployments
keewis d3316e9
correct the pin for `actions/setup-python`
keewis 23ada36
Merge branch 'main' into zizmor
VeckoTheGecko File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we also enforce sha pinning on the repo level?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we can try that after merging this PR |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related: We should also have this for Pixi when prefix-dev/pixi#5786 gets merged and released
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, we can do that, too. We'll have to be able to disable that for the nightly CI, though, otherwise the early warning system will be a week late.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking 3 days would be good. I think its ok if our nightly env is a few days late?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess so. The hope for using a cooldown is that if there is an attack, waiting for 7 days will allow others with more knowledge to detect and report the problem. Obviously, if everybody is doing this you won't gain anything.
However, my superficial knowledge on this topic is at its limit here, it might be worth raising this kind of question in the scientific-python discord: there are more security-aware folks and the authors of the scientific-python-nightly-wheels action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(drive-by comment from the Discord thread on this): I'm of the opinion that the latest nightly can be used in a very sandboxed, very scoped down job, just to test compatibility but with no acces to anything else. The container where that job runs is deleted after the job runs, so it cannot poison future runs of same or other workflows. Static analysis of the package to detect vulns, exploits, is possible, if wanted