-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
ci/permissions: Restrict permissions for remaining workflows #31603
Conversation
cc @mmorel-35 - not sure if we need to add some back in jobs |
What do you mean by "back in jobs" ? |
Signed-off-by: Ryan Northey <ryan@synca.io>
5024ef9
to
dac49b0
Compare
provide job-level permissions |
OK, Usually, I'm using https://app.stepsecurity.io/secureworkflow to help defining the right configuration : Is this also what you did ? |
no - i generally define them by hand (after checking the docs and the action) in this case im responding to a scorecard alert that these wfs dont have global token restrictions |
@@ -1,5 +1,8 @@ | |||
name: 'Sync downstream' | |||
|
|||
permissions: | |||
contents: read |
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.
this one is good - it uses appauth
afaict - this is what is required for codeql permissions:
contents: read
security-events: write
pull-requests: read |
which i think is already covered - except perhaps read perms in a private repo - ill update |
Signed-off-by: Ryan Northey <ryan@synca.io>
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.
LGTM. Thanks.
/retest |
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]