Give write access to backport action explicitly #61626
Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
cc: @dougbu as this might affect y'all as well. |
| permissions: | ||
| contents: write | ||
| issues: read | ||
| pull-requests: write |
There was a problem hiding this comment.
@hoyosjs I get pull-requests: write but why is write needed for contents or read for issues❔
There was a problem hiding this comment.
I expected
permissions:
contents: read
pull-requests: write
There was a problem hiding this comment.
All comments fall under "issues" in the GitHub API IIRC, even PR comments, so that's why read is required for issues.
write is probably required for contents since this workflow creates a new branch and commits as part of how it functions.
There was a problem hiding this comment.
pull-requests: write is only for the explicit action to create the pull request from one branch to another.
There was a problem hiding this comment.
Yes, exactly those scopes are why I gave it those permissions. @vcsjones do you know if this is correct?
There was a problem hiding this comment.
You might need write on issues because the backport bot leaves a comment on PRs (like these) that the back port has been started. @jkoritzinsky is right, PR comments are "issues" (also evidence of this that this backport bot triggers on issue_comment.
There was a problem hiding this comment.
I forgot about the reply. Much appreciated @vcsjones
ghost
locked as resolved and limited conversation to collaborators
No description provided.