Just a preface to emphasise that this is not a whinge that I think Zola is fantastic and great work!!!
I am not sure what I have done wrong, but I successfully ran the GitHub actions and it not only overwrote my repo but it also deleted the repo history. Fortunately, I still have a local commit for the repo. But this is concerning. This workflow needs to be explained better to prevent noobs (like me!) from losing their websites.
Steps to replicate:
- Have a GitHub repo myname.github.io for your Zola project.
- Run the GitHub action to deploy Zola in /docs
- Website didn’t work
- Try again point to the root of the repo
- Repo is completely replaced by the build files and no git history remains.
So I have one question and one suggestion.
The question is:
Should I be using a different repo than
myname/mywebsite and build this so that it ends up in
PS: I have a custom domain name,
myname.dev associated with
My suggestion is that there needs to be a warning here in the instructions to steer users away from this problem.
I think that my problem was that I thought that gh-pages branch should be replaced by my source branch. Because I used my source branch, then my source was overwritten.