Comments on "Resource not accessible by personal access token" error (fixed by adding Actions: Read-only permission) #1048
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Not sure if this is a bug report or documentation request or just me leaving a breadcrumb for other users ...
Maybe I missed this in the docs somewhere, but it would be helpful if the README spelled out which permissions a user should select when configuring a Personal Access Token for Release Please.
While it was easy enough to infer that Contents and Pull requests permissions were needed (based on the
permissions
field in the sample release-please.yml file), with only those permissions selected this GH action was spitting "Resource not accessible by personal access token" errors.I ended up having to enable the Actions permission to fix the issue, which I don't see mentioned in the docs. Ultimately, I ended up granting the following permissions on the PAT:
The text was updated successfully, but these errors were encountered: