-
Notifications
You must be signed in to change notification settings - Fork 1.2k
chore: restrict GitHub workflow permissions - future-proof #5276
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
chore: restrict GitHub workflow permissions - future-proof #5276
Conversation
Signed-off-by: Melissa Kilby <[email protected]>
|
May I kindly check in on the status of this PR? Thank you. |
| name: Create PR to merge release branch into the main branch | ||
| # At the end of a release cycle, we may want to automatically include all changes to release branches on the main branch to avoid the need for cherry-picking changes back to release branches | ||
| # This workflow can be disabled earlier in the release cycle in the GitHub UI as described in https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow | ||
| permissions: |
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.
Same question I asked in different PR in swift-format.
How does this change impact the permissions set inside jobs.
permissions:
contents: write
pull-requests: 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.
See answer in the swift-format PR: swiftlang/swift-format#1073 (comment)
|
Thanks for approving the PR, what are the next steps? Thanks. |
|
@swift-ci please test |
|
Hmm the Windows CI still appears to block merging ... any ideas on how to unblock this PR? Thanks a bunch! |
|
@swift-ci please test Windows platform |
|
@jmschonfeld and @shahmishal CI is cleared - may I kindly check in on the status of this PR? Thank you. |
See swiftlang/github-workflows#167 for additional context
This approach aligns with security best practices, as detailed in the following documentation: