Deployment to git repository works but website is not deployed

[nicolas-van]

I have a strange behavior here, which is not strictly related to this action but kinds of defeat its purpose.

Here is a quite trivial repository showing this problem: https://github.com/nicolas-van/hugotest (the attached workflow: https://github.com/nicolas-van/hugotest/blob/master/.github/workflows/hugo.yml )

When I commit something the workflow performs correctly ( https://github.com/nicolas-van/hugotest/actions ) and I can validate it did deploy correctly to the gh-pages branch.

But when I take a look at the deployments ( https://github.com/nicolas-van/hugotest/deployments ) I can see that Github just didn't care re-deploying my website to its static content server. He doesn't seem to understand that there is a new version on the gh-pages branch and doesn't care re-deploying.

I suppose it has something to do with the fact that this action just erase all the commits on the gh-pages branch and make a force push. When I edit a file on that branch (thus creating a new commit) Github seems to detect it correctly and re-deploy my Github Pages site.

Does anyone else has encountered that problem ? If I'm not the only one maybe we could consider adding a mode similar to what Travis uses ( See keep_history https://docs.travis-ci.com/user/deployment/pages/).

[nicolas-van]

Nevermind, it seems like this is just a duplicate of #9

[github-actions]

This issue has been LOCKED because of it being resolved!

The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.

Log | Bot Usage