actions/jekyll-build-pages

A simple GitHub Action for producing Jekyll build artifacts compatible with GitHub Pages.

jekyll-build-pages

A simple GitHub Action for producing Jekyll build artifacts compatible with GitHub Pages.

Scope

This is used along with actions/deploy-pages as part of the official support for building Pages with Actions (currently in public beta for public repositories).

Usage

A basic Pages deployment workflow with the jekyll-build-pages action looks like this.

name: Build Jekyll site
on:
 push:
   branches: ["main"]
permissions:
  contents: read
  pages: write
  id-token: write
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Setup Pages
        uses: actions/configure-pages@v5
      - name: Build
        uses: actions/jekyll-build-pages@v1
      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
  deploy:
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}

To write to a different destination directory, match the inputs of both the jekyll-build-pages and upload-pages-artifact actions.

steps:
  - name: Build
    uses: actions/jekyll-build-pages@v1
    with:
      destination: "./output"
  - name: Upload artifact
    uses: actions/upload-pages-artifact@v3
    with:
      path: "./output"

Action inputs

Input	Default	Description
source	./	The directory to build from
destination	./_site	The directory to write output into (this should match the path input of the actions/upload-pages-artifact action)
future	false	If true, writes content dated in the future
build_revision	$GITHUB_SHA	The SHA-1 of the Git commit for which the build is running
verbose	false	If true, prints verbose output in logs
token	$GITHUB_TOKEN	The GitHub token used to authenticate API requests

Release instructions

In order to release a new version of this Action:

1. Locate the semantic version of the upcoming release (a draft is maintained by the draft-release workflow).

2. Prepare a pull request to update action.yml to reference the incoming version, get it approved, and merge it into the main branch.

3. Publish the draft release as a pre-release from the main branch with semantic version as the tag name, with:

   • the checkbox to publish to the GitHub Marketplace checked ☑️
   • ⚠️ AND the checkbox to Set as a pre-release checked. ☑️

4. This will kick off a Docker publishing workflow for the newly created tag. Check the associated workflow run list to verify the new Docker image is created successfully before moving on to the next step.

5. After the Docker image has been created with the new tag, find that same pre-release and edit it. Update it with the checkbox to Set as the latest release checked ☑️ and then publish it again.

6. After publishing it as the latest release, the release workflow will automatically run to create/update the corresponding the major version tag such as v1.

   ⚠️ Environment approval is required. Check the Release workflow run list.

License

The scripts and documentation in this project are released under the MIT License.

jekyll-build-pages's Issues

If Actions are disabled for the repository, there are no error messages

Before finding the change with the public beta, I had actions disabled on repository level. If actions are disabled, there are no error messages, in the in the pages configuration or when pushing to the branch to be deployed

found these under Actions after enabling actions for the repository,

Use with Corporate Registry

Hi would it be possible to change the image URL or make it configurable so that we could use it with our own registry?
Our runners are not allowed to access the internet but we have an internal artifactory where we could pull the image from.

runs:
  using: 'docker'
  image: 'docker://ghcr.io/actions/jekyll-build-pages:v1.0.6'

Or would it be easier to just fork it?

Can the output of `bundle check` be un-hidden?

I noticed a warning popping up in some of my builds recently:

Warning:  github-pages can't satisfy your Gemfile's dependencies.

Example: this workflow.

It seems that this is due to the change in #61, but I was a bit stumped which dependency this would be – my Gemfile is just this:

source "https://rubygems.org"

ruby "2.7.4"

gem "github-pages", "~> 228", group: :jekyll_plugins

As it turns out, the warning is due to a version mismatch in Gemfile.lock, but because the output is thrown away (>/dev/null 2>&1) here

jekyll-build-pages/entrypoint.sh

Line 17 in 98742cd

if test -e "$SOURCE_DIRECTORY/Gemfile" && ! bundle check --dry-run --gemfile "$SOURCE_DIRECTORY/Gemfile" >/dev/null 2>&1; then

I had to figure out with trial and error.

Would it make sense to not hide that output, to make figuring this out a little easier? For what it's worth, my Gemfile.lock is the result of bundle install on that minimal Gemfile, and when I run bundle check with the Gemfile provided by this action with my Gemfile.lock in the container provided by this action, I get

$ bundle check --dry-run --gemfile Gemfile
Resolving dependencies...
The following gems are missing
 * nokogiri (1.14.1)
Install missing gems with `bundle install`

which I assume is because the Dockerfile uses

jekyll-build-pages/Dockerfile

Line 13 in 98742cd

RUN NOKOGIRI_USE_SYSTEM_LIBRARIES=true bundle install

and having the action output include the missing gem would have made figuring this out way easier.

tl;dr, I suggest

@@ -14,7 +14,7 @@
 GITHUB_PAGES=$PAGES_GEM_HOME/bin/github-pages
 
 # Check if Gemfile's dependencies are satisfied or print a warning 
-if test -e "$SOURCE_DIRECTORY/Gemfile" && ! bundle check --dry-run --gemfile "$SOURCE_DIRECTORY/Gemfile" >/dev/null 2>&1; then
+if test -e "$SOURCE_DIRECTORY/Gemfile" && ! bundle check --dry-run --gemfile "$SOURCE_DIRECTORY/Gemfile"; then
   echo "::warning:: github-pages can't satisfy your Gemfile's dependencies."
 fi

because showing the output is helpful. Would such a PR be welcome?

error pulling image configuration: download failed after attempts=1: unauthorized: unauthenticated: User cannot be authenticated with the token provided.

Not sure what's going on, or if it's just a temporary error. I'm getting this error while trying to push changes to my Github Pages project:

  /usr/bin/docker pull ghcr.io/actions/jekyll-build-pages:v1.0.3
  v1.0.3: Pulling from actions/jekyll-build-pages
  eff15d958d66: Pulling fs layer
  923e91ae3a1b: Pulling fs layer
  2aa5d3a4a151: Pulling fs layer
  bc64adf2d0b2: Pulling fs layer
  bfc5cca7d80e: Pulling fs layer
  42572f4afcbf: Pulling fs layer
  b27df5854eb4: Pulling fs layer
  5e60654b9df2: Pulling fs layer
  ac62fa2975d4: Pulling fs layer
  056fdbce372a: Pulling fs layer
  bc64adf2d0b2: Waiting
  bfc5cca7d80e: Waiting
  42572f4afcbf: Waiting
  b27df5854eb4: Waiting
  056fdbce372a: Waiting
  5e60654b9df2: Waiting
  ac62fa2975d4: Waiting
  error pulling image configuration: download failed after attempts=1: unauthorized: unauthenticated: User cannot be authenticated with the token provided.
Error: Docker pull failed with exit code 1

See example build: https://github.com/soundasleep/stormcloak.games/runs/6446601014?check_suite_focus=true

.nojekyll being ignored

I have a blog on github pages, which I build myself and push the generated static files to gh-pages brach in docs folder. This works great.

I don't want github to automatically build my pages, so I have a .nojekyll file as shown here:

https://github.com/travisdowns/travisdowns.github.io/tree/c90b37dd2eb59b9c2bc58f1a48d8380cd67dc481

Still, this action is running and publishing (at least per the logs) to github pages.

How do I make it stop?

undefined method `excerpt_separator'

We are unable to build any of our GitHub Pages Jekyll sites as of v1.0.10 with the following error:

Error: undefined method `excerpt_separator' for #<Jekyll::Page @name="QuickStart.md"> 

The page referenced is any markdown file that has an excerpt set in the front matter. There is a large thread for this bug on the Jekyll repository:

jekyll/jekyll#9544

The fix seems to be switching to github actions and pointing at v1.0.9 of this jekyll-build-pages action. We'd rather not do that and fall out of date.

Is Gemfile ignored now?

I host my blog on github pages with jekyll.

In my Gemfile I added a plugin. But it doesn't work as I expected. After some research I found the file was excluded by the action.

What's the reason of doing so? And how could I add custom plugins? Adding _plugins fold might not be a good idea since the plugin has dependencies.

Struggling to host a txt file

I am trying to host a txt file using this action but struggling. Is there anything I can configure to get it to include txt files when generating the site?

The repository is:
https://github.com/tjrobinson/ageukreading-mta-sts/

The workflow is this, unaltered from the sample:
https://github.com/tjrobinson/ageukreading-mta-sts/blob/main/.github/workflows/jekyll-gh-pages.yml

I'm unable to get it to serve any of these files:

https://ma-sts.ageukreading.org.uk/test.txt
https://ma-sts.ageukreading.org.uk/testdir/test2.txt
https://ma-sts.ageukreading.org.uk/.well-known/ma-sts.txt

I can serve a HTML file though:

https://ma-sts.ageukreading.org.uk/htmltest.html

Many thanks!

Gemfile is ignored in new build setup?

Hi,
We have
https://github.com/abapGit/abapGit/tree/c0252083ffa46e6920ef9c4e797c6ffc75e01f5a/docs
with
https://github.com/abapGit/abapGit/blob/c0252083ffa46e6920ef9c4e797c6ffc75e01f5a/docs/Gemfile

moving this pages setup verbatim to the new setup gives the following error, see https://github.com/abapGit/docs.abapgit.org/runs/4557637625

I expect the new build process to work for pages that previously worked?

Outdated version of bundler

The version of bundler used with this github action is (2.1.4). According to the bundler rubygems website this is from January 2020 and by that already four years old.

The latest version as of today is 2.5.5 from 2024-01-18.

This poses not only a big concern to supported features but can also mean a massive security risk.

I strongly advice to upgrade to the latest version as soon as possible and on a regular basis.

there is no option to pass jekyll build options

the jekyll build command can be configured with many options (they can be seen by running jekyll build --help). For example:

 --config CONFIG_FILE[,CONFIG_FILE2,...]  Custom configuration file

I usually pass multiple config files to jekyll depending on the environment I am deploying to.

However this action do not provide a way to pass those options.

with future: false it is still showing all of my future blogs

From December end week future: false is not working. This was working previously.

Expected Behavior

I expected my site to not show the future blogs. I am using future: false.
Here is my action link https://github.com/rupeshtiwari/rupeshtiwari.github.io/actions
Check it is showing all of my future blogs https://www.rupeshtiwari.com/posts/

Current Behavior

It is showing all of the future dated blogs check this blog
https://www.rupeshtiwari.com/posts/
Here is my config file
https://github.com/rupeshtiwari/rupeshtiwari.github.io/blob/main/_config.yml

Configured source folder is not respected

Since a while back, I'm not able to deploy my site due to this issue. Looking at the build log, it's clear that the action is not respecting the source property of _config.yaml.

Repo for reference: https://github.com/ptz0n/ptz0n.github.io

_config.yaml:

source: ./src
…

build log:

Configuration file: /github/workspace/./_config.yml
      GitHub Pages: github-pages v226
      GitHub Pages: jekyll v3.9.2
             Theme: jekyll-theme-primer
      Theme source: /usr/local/bundle/gems/jekyll-theme-primer-0.6.0
         Requiring: jekyll-github-metadata
        Pagination: Pagination is enabled, but I couldn't find an index.html page to use as the pagination template. Skipping pagination.
         Requiring: jekyll-seo-tag
         Requiring: jekyll-sitemap
         Requiring: jekyll-redirect-from
         Requiring: jekyll-paginate
         Requiring: jekyll-coffeescript
         Requiring: jekyll-commonmark-ghpages
         Requiring: jekyll-gist
         Requiring: jekyll-github-metadata
         Requiring: jekyll-relative-links
         Requiring: jekyll-optional-front-matter
         Requiring: jekyll-readme-index
         Requiring: jekyll-default-layout
         Requiring: jekyll-titles-from-headings
   GitHub Metadata: Initializing...
            Source: /github/workspace/.
       Destination: /github/workspace/./_site

Introduced by: 39a7bb3#diff-6f9d41d046756f0ddc2fcee0626bdb50100d12b88f293734eff742818e03efa2R11

Related issue: #9

The problem

Executing jekyll build and passing the --source attribute overwrites anything you have defined in your _config.yaml.

Troubleshooting build errors states without any actionable pointers:

You changed the source setting in your _config.yml file. GitHub Pages overrides this setting during the build process.

Reading up on the Github Actions documentation, there is no way of passing inputs to this action. If there is a "magic" way, let's at least include it in the README.

Setting the environment/secret INPUT_SOURCE will not have any effect.

Possible solution

Not passing the --source argument to jekyll build, having Jekyll default this attribute to ./ or respecting what's in the configuration file.

Does not support native GitHub Pages MermaidJs support.

I want to be able to copy and paste a index.md file from a GitHub repo where it renders with MermaidJS just fine, and have it render effectively the same diagram after being rendered on GH Pages.

The current build system actively corrupts Mermaid rendered files and makes them impossible to render as expected.

The fact that safe=true is hard coded means we cant add a plugin that would support this to the default pipeline without githubs help.

I'm trying to support efforts for the blind to be able to more easily communicate visual ideas to the sighted and this support is critical to allow that using MermaidJS. I am formally asking for all reasonable accommodation from GitHub and developers to support this goal.

Any way opt out of the public beta?

Hi,
Is there a way to not be part of the public beta?

My pages are breaking... #3, #4

jekyll-build-pages uses an unsupported version of Ruby

The Dockerfile for jekyll-build-pages uses Ruby 2.7.4, which is no longer supported. This is causing GitHub Pages Jekyll builds to fail.

The GitHub pages-gem has been updated to Ruby 3.3, the current stable version. Can jekyll-build-pages also be updated to use Ruby 3.3 (by updating the Dockerfile) and a new release deployed?

Startup failure

Try the A basic Pages deployment workflow

actions/checkout@v4, actions/configure-pages@v5, actions/jekyll-build-pages@v1, actions/upload-pages-artifact@v3, and actions/deploy-pages@v4 are not allowed

Unable to pull docker image

Hi -

My GitHub actions have stopped working today as it's unable to retrieve the docker ghcr.io/actions/jekyll-build-pages:v1.0.7
Not sure if the image has moved or if there's another tag. I attempted latest, v1.0.8 with no luck.

Receiving the following message

Error response from daemon: Head "https://ghcr.io/v2/actions/jekyll-build-pages/manifests/latest": Get "https://ghcr.io/token?scope=repository%3Aactions%2Fjekyll-build-pages%3Apull&service=ghcr.io": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Any assistance would be greatly appreciated!

Improve the troubleshooting experience of "Warning: github-pages can't satisfy your Gemfile's dependencies"

Sample run: https://github.com/4tals/LinksForIsrael/actions/runs/6586647478/job/17895361781#step:4:13

Run actions/jekyll-build-pages@v1
/usr/bin/docker run --name ghcrioactionsjekyllbuildpagesv108_f1e46c --label 6[9](https://github.com/4tals/LinksForIsrael/actions/runs/6586647478/job/17895361781#step:4:10)7884 --workdir /github/workspace --rm -e "INPUT_SOURCE" -e "INPUT_DESTINATION" -e "INPUT_TOKEN" -e "INPUT_FUTURE" -e "INPUT_BUILD_REVISION" -e "INPUT_VERBOSE" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_ID_TOKEN_REQUEST_URL" -e "ACTIONS_ID_TOKEN_REQUEST_TOKEN" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/LinksForIsrael/LinksForIsrael":"/github/workspace" ghcr.io/actions/jekyll-build-pages:v1.0.8
Bundler can't satisfy your Gemfile's dependencies.
Install missing gems with `bundle install`.
Warning:  github-pages can't satisfy your Gemfile's dependencies.

As you can see, it just says that the dependencies can't be satisfied. It would be very helpful to understand what dependencies exactly can't be satisfied and why - needless to say, it does not reproduce locally and sometimes the workaround can be simple (for example github/pages-gem#887).

Followup question #53

@yoannchaudet Let me re-phase the question.

My Github Action look like below

      - name: Building Jekyll output
        uses: actions/jekyll-build-pages@v1
        with:
          source: ./_docs
          destination: ./_site

So I try to add _config.yml on ./_docs however, it didn't load correctly. Put _config.yml on root is not a option as well because we develop monorepo and root are reserve for globally use config.

My idea is add another with for provide directory to _config.yml? What do you think

      - name: Building Jekyll output
        uses: actions/jekyll-build-pages@v1
        with:
          config: ./_docs/_config.yml
          source: ./_docs
          destination: ./_site

Originally posted by @kamontat in #53 (comment)

Github Pages as Actions to run automatically in forked repos

I successfully set up Actions pipeline from starter-workflows to replicate my classic Jekyll setup. However, these actions aren't run automatically in a forked repo. This was not the case with Classic pages, they would run&deploy in the forked repo automatically (especially, if the forked repo contained only gh-pages branch). Is there a way to replicate this behavior with Actions as well?

Basically, I'm building a website scaffolding/barebones that's intended to be forked. And ideally, it should already be enough and give a generated test webpage available online, without any extra configuration.

Enabling plugins

About GitHub Pages and Jekyll - GitHub Docs says that I should be able to add a plugin by name to the plugins value of _config.yml, but that doesn't seem to work. It suggests getting more info from Configuration | Jekyll • Simple, blog-aware, static sites, which doesn't really cover that, but has a link to Plugins | Jekyll • Simple, blog-aware, static sites that tries to help, but is immediately mired in details about a Gemfile and specifics that I don't have enough Ruby experience with to understand.

How do I add plugins like mermaid, AsciiDoc, &c?

Output directory permissions

Hi

I ran into an issue with permissions on the generated output folder.
The jekyll build output is as expected, but the download-artifact step fails due to missing permissions.
I tried adding - run: mkdir -p ./output/publish in between the two steps, but that fails due to missing permissions as well.

...
      - uses: actions/jekyll-build-pages@v1
        with:
          destination: ./output
      - uses: actions/download-artifact@v3
        with:
          path: ./output/publish
...

The workaround i have now is adding - run: mkdir ./output before the jekyll build step, which makes it have the necessary permissions.

How to configure _config.yml file?

Thank you 🙇‍♀ for wanting to create an issue in this repository. Before you do, please ensure you are filing the issue in the right place. Issues should only be opened on if the issue relates to code in this repository.

• If you have found a security issue please submit it here
• If you have questions about writing workflows or action files, then please visit the GitHub Community Forum's Actions Board
• If you are having an issue or question about GitHub Actions then please contact customer support

If your issue is relevant to this repository, please delete this text and continue to create this issue. Thank you in advance.

markdown: GFM does not include permalink contents

Docs say:

only our GFM processor will always match the results you see on GitHub

https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

I have a pages site configured with markdown: GFM but the way github renders my README.md is different than the jekyll generated page.

I reference a repository permalink in the markdown and github renders this inline in the page:

The jekyll generated site does not, it just renders the URL:

See https://github.com/rectalogic/pagetest

Run as non-root/Use the same UID and GID as the GitHub runners?

Hi! First of all thanks for this repo/including GitHub Pages in Actions, it's nice to finally be able to see what's happening with a Pages build and deployment plus now we can use the exact same way GitHub Pages does a build or deployment in our own CI :)

One small thing I ran into is that the Docker image runs as root, so the files written by the build are also owned by root.
Since the GitHub runners run as UID 1001 GID 121 they are then unable to make any changes to these files.
I'm not sure if there's a policy within GitHub for these things, but it might make sense to use the same UID/GID as the runners? Also not running as root is a plus of course :)

Bundler not installing dependencies, failing the build

Hey, I do believe my issue is coming from this action.

I recently attempted to upgrade Jekyll (and related) dependencies for my blog, which then failed the build as a result: https://github.com/milosmns/milosmns.github.io/actions/runs/7600750931/job/20699353764

What happened exactly:

• My local build failed due to bundler being incompatible with my ruby version
• I decide to upgrade everything
• SASS converter starts complaining that / (divide operator) is deprecated
• I migrate to math.div instead
• Local build passes
• I push to GitHub
• GitHub Pages action runs
• 💣

I understand that there are some limitations with GH Actions and ruby/bundler versions, but as I'm really not an expert at that, I was hoping that you already have a workaround. I couldn't find anything in the closed issues that fully matches my problem.

Thanks for the support!

Config Flag

Is it possible to pass a --config flag to the build command? Say, if we want to use an alternative config file for production builds?

Link to documentation or include sample workflow YAML in README

Hi friends!

I was looking at this repo and realized two quick things:

1. There's no link to the GitHub Pages section of the docs.github.com about how to use this action
2. There's no documentation at all about how to use this action

I think adding a new section like "Usage" with a link to the docs.github.com page for this would fit both needs, but it'd also be nice to have an example folks could copy-and-paste like what I see for setup-ruby: https://github.com/ruby/setup-ruby#usage

Thanks for considering!

cc @yoannchaudet

pulling the action image is slow

as can be seen in e.g. https://github.com/staabm/staabm.github.io/runs/7689001778?check_suite_focus=true pulling the ghcr.io/actions/jekyll-build-pages:v1.0.4 takes most of the time of the action to run.

I guess this is related to the number of layers this docker container has:

  /usr/bin/docker pull ghcr.io/actions/jekyll-build-pages:v1.0.4
  v1.0.4: Pulling from actions/jekyll-build-pages
  eff15d958d66: Pulling fs layer
  923e91ae3a1b: Pulling fs layer
  2aa5d3a4a151: Pulling fs layer
  bc64adf2d0b2: Pulling fs layer
  bfc5cca7d80e: Pulling fs layer
  61b6e3e25463: Pulling fs layer
  7c62fb63f605: Pulling fs layer
  0f68cc81f8f6: Pulling fs layer
  09f325326117: Pulling fs layer
  a73a0a50c4db: Pulling fs layer
  bc64adf2d0b2: Waiting
  bfc5cca7d80e: Waiting
  61b6e3e25463: Waiting
  7c62fb63f605: Waiting
  0f68cc81f8f6: Waiting
  09f325326117: Waiting
  a73a0a50c4db: Waiting
  2aa5d3a4a151: Verifying Checksum
  2aa5d3a4a151: Download complete
  923e91ae3a1b: Verifying Checksum
  923e91ae3a1b: Download complete
  eff15d958d66: Verifying Checksum
  eff15d958d66: Download complete
  bfc5cca7d80e: Verifying Checksum
  bfc5cca7d80e: Download complete
  bc64adf2d0b2: Verifying Checksum
  bc64adf2d0b2: Download complete
  7c62fb63f605: Verifying Checksum
  7c62fb63f605: Download complete
  09f325326117: Verifying Checksum
  09f325326117: Download complete
  0f68cc81f8f6: Verifying Checksum
  0f68cc81f8f6: Download complete
  a73a0a50c4db: Verifying Checksum
  a73a0a50c4db: Download complete
  61b6e3e25463: Verifying Checksum
  61b6e3e25463: Download complete
  eff15d958d66: Pull complete
  923e91ae3a1b: Pull complete
  2aa5d3a4a151: Pull complete
  bc64adf2d0b2: Pull complete
  bfc5cca7d80e: Pull complete
  61b6e3e25463: Pull complete
  7c62fb63f605: Pull complete
  0f68cc81f8f6: Pull complete
  09f325326117: Pull complete
  a73a0a50c4db: Pull complete
  Digest: sha256:e56d7e4c5ac45aa2934b1d535f4c66769a442ef6538c7948f8b4e3b2950fd7b4
  Status: Downloaded newer image for ghcr.io/actions/jekyll-build-pages:v1.0.4
  ghcr.io/actions/jekyll-build-pages:v1.0.4

would it be possible to reduce the numer of layers to speedup the built?

Running jekyll-build-pages action fails due to invalid docker token

EDIT: Apparently this was caused by GitHub and not by this Action. My bad for jumping the gun :(

Our GitHub page building workflow fails due to error in jekyll-build-pages action

Full log can be found:
https://github.com/qentinelqi/qweb/runs/7003372901?check_suite_focus=true

Pull down action image 'ghcr.io/actions/jekyll-build-pages:v1.0.3'
  /usr/bin/docker pull ghcr.io/actions/jekyll-build-pages:v1.0.3
  v1.0.3: Pulling from actions/jekyll-build-pages
  eff15d958d66: Pulling fs layer
  923e91ae3a1b: Pulling fs layer
  2aa5d3a4a151: Pulling fs layer
  bc64adf2d0b2: Pulling fs layer
  bfc5cca7d80e: Pulling fs layer
  42572f4afcbf: Pulling fs layer
  b27df5854eb4: Pulling fs layer
  5e60654b9df2: Pulling fs layer
  ac62fa2975d4: Pulling fs layer
  056fdbce372a: Pulling fs layer
  bfc5cca7d80e: Waiting
  42572f4afcbf: Waiting
  b27df5854eb4: Waiting
  5e60654b9df2: Waiting
  ac62fa2975d4: Waiting
  056fdbce372a: Waiting
  bc64adf2d0b2: Waiting
  error pulling image configuration: download failed after attempts=1: unauthorized: unauthenticated: User cannot be authenticated with the token provided.
  Warning: Docker pull failed with exit code 1, back off 3.985 seconds before retry.