-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment to git repository works but website is not deployed #18
Labels
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:/nicolas-van/hugotest (the attached workflow: https:/nicolas-van/hugotest/blob/master/.github/workflows/hugo.yml )
When I commit something the workflow performs correctly ( https:/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:/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/).The text was updated successfully, but these errors were encountered: