actions-hugo VS terraform-provider-github

You can build your Hugo site in your Github Actions, e.g. like in https://github.com/peaceiris/actions-hugo, then push the static pages to your server

Documentation provides an example workflow file that uses GitHub Actions for Hugo action in the "Build Hugo With GitHub Action" section. It is ok to use it, but I will use combination of 2 examples (1, 2) from GitHub Actions for Hugo's README because it has one for projects using PostCSS.

If the data fetch from previous step succeeds, the workflow continues by building the static website with Hugo. Hugo is setup using action peaceiris/actions-hugo. When the files are ready, the result is published to GitHub pages, using another GitHub action, peaceiris/actions-gh-pages.

Luckily, there is a workflow for it. By implementing peaceiris/actions-hugo@v2 on my GitHub workflow, I was able to achieve what I wanted to do. Simple as that.

Less is more IMO. A Github Action using Hugo to deploy to GH pages.

For more information about the actions used and their options, please see Hugo and Github pages on Github.

I am looking for someone who can help me, pro bono, to: - set up this site using GitHub Pages - set up Hugo SSG (https://gohugo.io) using Jane (https://github.com/xianmin/hugo-theme-jane) as the theme - set up automatic building using GitHub actions perhaps using https://github.com/peaceiris/actions-hugo - set up Giscus (https://giscus.app) for comments (may need to fork theme, if so try to up a steam a PR also so a separate fork does not need to be maintained.) - set up banner art and profile picture (may need to fork theme, if so try to up a steam a PR also so a separate fork does not need to be maintained.) - set up SEO, RSS, favicon, Analytics, etc.

View on GitHub

I set up Hugo with peaceiris/actions-hugo. The build step afterwards runs the command

There's an open feature request issue for it in the provider. I'd keep your eyes on 1534 for it to be implemented, as well as give it the 'ol thumbs-up bump.

I wanted to configure GitHub Pages using terraform because this project already uses it to configure this repository. But currently, due to how GitHub provider for terraform is written, configuring Pages requires some fiddling and will not work on the first run. During my research into how I could achieve declarative configuration for Pages, I found out that GitHub recently added actions that allow deploying to Pages without additional branch. I like this new approach better and in the future I will switch to it, but for now I decided to configure Pages manually as suggested by GitHub Pages Action that we are using.

Someone hit the wrong switch at the factory: https://github.com/integrations/terraform-provider-github/releases/tag/v4.28.0

Well, there are a lot of open issues [0] with no outlook to get them ever closed.

We've had issues with branch protection rules (the same code works with old actors in the state, but new actors erroring out without any reason), organization secrets, etc.

[0]: https://github.com/integrations/terraform-provider-github/is...

https://github.com/integrations/terraform-provider-github/is...

I don't understand how this hasn't gotten more attention throughout the years. I would like to learn about why that is.

I am a big fan of Squash and Merge but it's saddening that users have to configure that by hand on a repo when they first merge a commit via the GitHub UI, as many people aren't aware or don't think about it which can lead to nasty commit histories.

Am I missing something? Am I git'ing wrong?