I think the pr-commands.yaml, document.yaml, and render-rmarkdown.yaml were also missing contents write permissions. So I have added that to those and regenerated examples/README.md

Can confirm this issue for the (canonical) blogdown workflow. Without the write permission, the final "Deploy to GitHub Pages" step will have trouble writing to the gh-pages branch with the following error:

Force-pushing changes...
/usr/bin/git push --force ***github.com/<user>/<user>.github.io.git github-pages-deploy-action/b7eexlozc:gh-pages
remote: Permission to <user>/<user>.github.io.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/<user>/<user>.github.io.git/': The requested URL returned error: 403
...
Error: The deploy step encountered an error: The process '/usr/bin/git' failed with exit code 128 ❌
Notice: Deployment failed! ❌

This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this pull request.