Publish Jekyll locally generated main branch _site subdir to gh-pages branch for GitHub Pages User site? #596
-
I'd like to use GitHub Pages to host my user Blog site. I'd like to have Jekyll build my site locally (to on:
# Triggers the workflow on push requests to the main branch if the commit includes a tag that matches the Semantic Version release tag
push:
# tags: [ releases/\d+\.\d+\.\d+ ]
branches: [ main ]
# This line allows you to run this workflow manually from the Actions tab
workflow_dispatch: Although I have not released any release tags yet, I have that tags conditional commented out, to run the action and deploy on every commit until I get the Deploy action working. The deploy step looks like this: - name: Deploy
uses: peaceiris/actions-gh-pages@v3
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
publish_dir: ./_site # the action will deploy the <repository root>/_site contents to the (default) gh-pages branch, root directory But it is not working. Is it possible to use I'm in the very early stage of building the site. It's public, at Bill.Hertzing.github.io. I'd certainly appreciate it if you could let me know what's wrong with my Deploy step. There is also the first technical post with lots of details, and at it's end you can see the step I'm stuck on Thanks for your work on creating this action! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It looks working for me. https://github.com/BillHertzing/BillHertzing.github.io/tree/109dc69638e0246f4eece7e79c1e98b52d7cb631
We can ignore this message (copying dotfiles.) This will be hidden in the feature release. And, GitHub Pages has the native Jekyll building feature without GitHub Actions. Why did you use GitHub Actions with Jekyll? Just curious. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the quick response. I re-tried it, and it is working. I must have made a user error. I may want to eventually develop a Jekyll Plugin and I know I'll want to eventually publish my own Jekyll theme, so might as well start with an approach that will support that. Because I want to use the latest Ruby and MSYS2 components, non-approved Jekyll Plugins and a non-approved Jekyll theme, I will keep the site source code under the Kudos on this great OSS GitHub Action! |
Beta Was this translation helpful? Give feedback.
It looks working for me. https://github.com/BillHertzing/BillHertzing.github.io/tree/109dc69638e0246f4eece7e79c1e98b52d7cb631
We can ignore this message (copying dotfiles.) This will be hidden in the feature release.
And, GitHub Pages has the native Jekyll building feature without GitHub Actions. Why did you use GitHub Actions with Jekyll? Just curious.