Problem with Github token

[tomgue]

When I try to edit a file in Sveltia CMS, I get this error, I can't edit my files. I think I've configured the token correctly.

Thanks for the great work you do, @kyoshino.

[kyoshino]

Claude investigated the issue and wrote a response 🙂

Thanks for the report! The token itself is fine — the problem is that your config has publish_mode: editorial_workflow, and in that mode saving an entry doesn't just commit: Sveltia CMS creates a cms/… branch, commits to it, then opens a pull request. Your token has Contents: Read and write, so the branch and commit succeed, but opening the PR needs Pull requests: Read and write, which the token doesn't have. That's what “Resource not accessible by personal access token” is telling you. You can actually see it in your repo: there are six cms/* branches with your saved changes but no pull requests.

To fix it, edit the token at https://github.com/settings/personal-access-tokens, and under Repository permissions add Pull requests → Read and write. After that, saving will open the PR, and Publish in the CMS will merge it. The existing cms/* branches will be picked up on your next save of each entry, or you can just delete them.

I'll also improve the CMS here: the “generate a token” link on the sign-in screen will pre-select the Pull requests permission when Editorial Workflow is enabled, and the dialog will say the token needs it.

[tomgue]

Claude is right, that was indeed the problem!
Thanks !

[kyoshino]

Fixed the in-product token generation link in v0.217.0. Sorry for the inconvenience!