-
Notifications
You must be signed in to change notification settings - Fork 154
chore(ci): sets base permissions on all workflows #1801
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
Conversation
adds pull requests write permission add permissions for packages, id-token add permissions add permissions all the permissions!
Kudos, SonarCloud Quality Gate passed! |
@@ -32,6 +40,9 @@ jobs: | |||
env: | |||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |||
release_label_on_merge: | |||
permissions: | |||
pull-requests: read | |||
contents: write |
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.
Can this contents: write
be scoped down only to issues?
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.
With issues: write
yes, but removing content would not prevent from merge, or?
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.
Looking good as far as I can tell - left one comment/question only
adds pull requests write permission add permissions for packages, id-token add permissions add permissions all the permissions!
Description of your changes
Adds a root
permissions
to the base of every workflow that was missing one.Related issues, RFCs
Issue number: #1799
Checklist
Breaking change checklist
Is it a breaking change?: NO
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.