-
Notifications
You must be signed in to change notification settings - Fork 3.8k
chore: update assignment workflow permissions for v12 #8947
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: update assignment workflow permissions for v12 #8947
Conversation
* chore: Try another workflow permission. * chore: Explicitly specify the GitHub token. * chore: Try with contents: write. * chore: Try write-all at the top level. * chore: try regular pull_request. * chore: Fix assign reviewers action configuration.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
BenHenning
left a comment
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.
Self-reviewed to verify parity with #8811.
|
NB: As with #8811, the assignee workflow won't be fixed until after this PR is merged. |
|
PTAL @cpcallen. |
|
Thanks @cpcallen. Since this is a small win and generally negligible, will go ahead and merge. |
b8c2b73
into
RaspberryPiFoundation:rc/v12.0.0
This is a cherry-pick of #8811 into the v12 release branch.
The basics
(ish--largely relying on the original testing for this PR since it's actions-related)
The details
Resolves
This fixes the same issue as #8811 but on the v12 branch.
Proposed Changes
See #8811.
Reason for Changes
The failing assignee workflow will continue on v12 so the cherry-pick makes the next couple of PRs for this branch a bit nicer, but it's not a strong must-have since we'll eventually merge
developintov12which would then include #8811.Test Coverage
N/A -- There's no strong benefit from automated tests for this workflow, and it was manually tested as part of #8811 (see #8811 (comment)).
Documentation
N/A -- No documentation changes are needed for this.
Additional Information
None.