-
Notifications
You must be signed in to change notification settings - Fork 22
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
GitHub token requires read/write permissions #55
Comments
Actually, no idea either. Try creating a tag, which the new release should refer to, manually for the time being |
Apparently you have to use |
Could somebody give me a link to a blog post or something that reflects the changes of the new token format, please? I've clearly missed something :D |
Ah, sorry. I've searched through GitHub's changelog a bit, and it seems like this change is the culprit. Edit: See this paragraph for the exact format differences |
Oh, that makes a lot of sense now! Thank you. Also, I see now why I didn't notice it earlier - it's been a while since I created new repositories, and the old ones still have read/write permissions by default. @MattiDragon, so, all you need to do is go to your repository's settings, Let me know if the problem persists! |
Another workaround for this is to manually specify the permission grant for the jobs:
my_release:
runs-on: ubuntu-latest
permissions:
contents: write # <- add this
steps:
# ... This allow the workflow job to modify github releases, so you don't need to configure your repository setting manually See: |
My publish workflow has failed to publish to git twice now:
I have manually published the releases, so that's why you see them.
I have no idea why it's broken, but it is
The text was updated successfully, but these errors were encountered: