peaceiris / actions-hugo

GitHub Actions for Hugo ⚡️ Setup Hugo quickly and build your site fast. Hugo extended, Hugo Modules, Linux (Ubuntu), macOS, and Windows are supported.
https://github.com/marketplace/actions/hugo-setup
MIT License
1.38k stars 80 forks source link

support: Hugo not deploying to gh-pages branch #578

Closed Xevion closed 2 years ago

Xevion commented 2 years ago

Checklist

Describe your question

Why is my Hugo Deploy Action not deploying to my gh-pages branch correctly?

Relevant links

Public repository: https://github.com/Xevion/powershell/
TOML* config: https://github.com/Xevion/powershell/blob/7abb7a6bf5c5f58b46d8ef80514e2deda53d0ae6/config.toml
YAML workflow: https://github.com/Xevion/powershell/blob/7abb7a6bf5c5f58b46d8ef80514e2deda53d0ae6/.github/workflows/gh-pages.yml

Relevant log output

No relevant log output. Check latest action as of time of issue creation for details.

Additional context.

I have everything set up correctly to the best of my knowledge. The submodule for the theme exists, it runs on my local machine with the version provided correctly. I've read both the Actions repo README and the Hugo Actions repo's README several times. My action deploys without error. The repository is set to use the gh-pages branch as mentioned. I've tried using /docs and /<root>, and switched around the Workflow YML configuration several times, but nothing has worked. Currently, Jekyll's README deploys, so I'm not sure what to make of that.

I really do apologize if it's something obvious, but I've exhausted all ideas on how to get this working and Google won't give me any useful suggestions.

Thanks.

Xevion commented 2 years ago

Apologies for opening up the issue. After leaving the issue alone and coming back to it later tonight, I was able to just now fix it.

I apologize if I wasted anyone time with this issue.

peaceiris commented 2 years ago

Thanks, great notes! Enjoy Hugo ʕ◔ϖ◔ʔ

github-actions[bot] commented 2 years ago

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