pkgdown fails to deploy to GH pages

[astamm]

I set up the pkgdown GHA script for one of my packages but it seems that the step JamesIves/[email protected] fails because of this error:

/usr/bin/git push --force ***github.com/astamm/mascot.git github-pages-deploy-action/wkcfwuxcv:gh-pages
[50](https://github.com/astamm/mascot/runs/6479064067?check_suite_focus=true#step:7:51)
remote: Permission to astamm/mascot.git denied to github-actions[bot].
[51](https://github.com/astamm/mascot/runs/6479064067?check_suite_focus=true#step:7:52)
fatal: unable to access 'https://github.com/astamm/mascot.git/': The requested URL returned error: 403

which further triggers:

Error: The deploy step encountered an error: The process '/usr/bin/git' failed with exit code 128 ❌
[57](https://github.com/astamm/mascot/runs/6479064067?check_suite_focus=true#step:7:58)
Deployment failed! ❌

Since I have not seen this problem with my other packages, I wonder whether it might have something to do with the fact that this one has files versioned via Git LFS. Is there some special setup that need careful attention when using the pkgdown workflow on Git LFS repos?
I originally thought the problem was a misuse of the actions/checkout@v2 GHA, but the check-standard workflow also uses it and works smoothly.

[gaborcsardi]

This does not seem like an issue with r-lib/actions to me. You can try to update the version of https://github.com/JamesIves/github-pages-deploy-action, it seems that @v4.3.3 is the latest.

You can also double check the default actions permissions of your repository, in Settings -> Actions -> General. For pkgdown deployment you need read and write workflow permissions.

[astamm]

Thanks for your reply @gaborcsardi. It seems indeed that updating actions/checkout to v3 and JamesIves/github-pages-deploy-action to v4.3.3 did the trick.
It might be regarded as an issue with r-lib/actions though as this version updates should be performed I think.
Thank you anyway.

[gaborcsardi]

Are both updates needed?

[astamm]

Since the check-standard workflow works well with actions/checkout@v2, I would say only JamesIves/[email protected] matters.

[astamm]

I was wrong, sorry. My problem might have been caused by lack of permissions. I double check and get back with a proper solution.

[astamm]

Confirmed it was a permission issue. Sorry for filing this here.

[github-actions]

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