Deploy a Jekyll 4 site to GH Pages using the "Jekyll Actions" action
A live demo and introduction around deploying Jekyll 4 to GitHub Pages - using a GitHub Actions workflow and the Jekyll Actions action. If you prefer to use a more generic Ruby action to setup your environment, see my related quickstart - jekyll-github-actions-quickstart.
The reason why we use GitHub Actions to build our Jekyll site is that it gives us more control of the environment and build flow. Like using Jekyll 4 instead of Jekyll 3, using custom gems and adding in shell, Python, or Node.js commands before the Jekyll build command.
If you are new to GH Actions, see links and code snippets in my Workflow Builder project.
Follow one of the approaches below to learn how it works and set up your own site and workflow.
This project was developed as part of writing a step-by-step guide for the Jekyll site's documentation.
Here is the link:
See this project's live demo hosted on GitHub Pages:
Create your own repo like this one using the button below. Then continue following the setup and run instructions on this page.
There are many ways to deploy a Jekyll site on GH Pages. I cover some in my Code Cookbook.
Those approaches have different levels of complexity:
The approaches have varying levels of security.
GITHUB_TOKEN
. This only has access to one repo during workflow a run, is never seen by a human and so is very secure.How to install and run locally and deploy on GH Pages
LICENSE
to LICENSE-source
and then modify LICENSE
with your own name.