gh-pages deploy failure

[dalance]

In README and example, GITHUB_TOKEN is used to push.
Currently this causes failure of pages deploy.

https://github.saobby.my.eu.orgmunity/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/td-p/26869

Alternatively personal access token can be used.

peaceiris/actions-gh-pages may be usable, but I didn't confirm.

[rhysd]

Hmm, but example workflows in this repository are able to push gh-pages branch to remote.

• Source: https://github.com/rhysd/github-action-benchmark/blob/master/.github/workflows/rust.yml
• Log: https://github.com/rhysd/github-action-benchmark/commit/505be0a00dfcf056e707f1a060b249dc681ad8cb/checks?check_suite_id=306722379

I think the problem GITHUB_TOKEN which cannot push to remote happens only within action. Environment which runs action is different from one which runs workflow. Workflow seems to be able to push branch to remote.

github-action-benchmark does not push to remote by itself. Pushing to remote is done by user in workflow. So I think the action can avoid the issue you reported.

[dalance]

Sorry. push is success, but pages deploy is failed.
In my project, "Settings" -> "GitHub Pages" shows "build failed" after pushing by GITHUB_TOKEN.

[dalance]

For example, https://rhysd.github.io/github-action-benchmark/dev/bench/ shows the latest commit is b652625.
But the latest build https://github.com/rhysd/github-action-benchmark/runs/299122357 is success.
So the latest commit should be 505be0a.
The deploy of pages seems to be continuously failed since b652625.

[rhysd]

Ahh, I understood. For some development reason, I pushed gh-pages from my local machine. The commit at that time deployed gh-pages successfully. But other commits pushed by action fail.

Thank you for the point. As of now, we need to use personal token. I'll update this repository and include note about this in README.

[rhysd]

I confirmed using personal access token with no scope could build gh-pages.

[rhysd]

I updated example workflows to use personal access token. And added an extra step to register a personal access token in basic usage section of README.md. I believe they are sufficient to close this issue. Thank you for reporting this.

[dalance]

Thank you for your quick response.

[WizardOfMenlo]

Hi there. Just wanted to point out that as of now I tested and deploying GitHub pages with the GITHUB_TOKEN seems to be working properly, so the extra steps should not be needed anymore.