GITHUB_TOKEN permissions that needs write access
See original GitHub issueSince it’s now possible to control the permissions of the GITHUB_TOKEN
on a job basis (https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/) it would be nice to know what permissions need write access to get this job to work.
I’ve currently set all of my repos permissions to read
and then the job failed using this action with the following error
After reading the readme I found that this is expected and is caused by not having the correct permissions. So it would be really awesome if it could be added to the readme what permissions are required to have write access for this action to work.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Automatic token authentication - GitHub Docs
You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are...
Read more >GitHub Actions: Control permissions for GITHUB_TOKEN
GitHub Actions now lets you control the permissions granted to the GITHUB_TOKEN secret. The GITHUB_TOKEN is an automatically generated secret ...
Read more >Token permissions for GitHub Actions - Damir's Corner
GitHub Actions provide a default GITHUB_TOKEN that can be used by steps in your workflow that require access to your GitHub repository.
Read more >What permissions does GITHUB_TOKEN require for releases ...
To allow your GitHub Action creating a draft release, you will have to grant your GITHUB_TOKEN access to POST /repos/:owner/:repo/releases ...
Read more >How it works, Change Permissions, Customizations - YouTube
We will also see of course what is GITHUB_TOKEN and how the GitHub token authentication works. EXCLUSIVE CONTENT Do you want...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
What worked for me in the end was setting the
pull-requests
scope towrite
permission.I’ve updated the readme with details of the scopes required. Thank you for raising this and investigating!