Skip to content
actions

GitHub Action

Upload GitHub Pages artifact

v3.0.1 Latest version

Upload GitHub Pages artifact

actions

Upload GitHub Pages artifact

A composite action that prepares your static assets to be deployed to GitHub Pages

Installation

Copy and paste the following snippet into your .yml file.

              

- name: Upload GitHub Pages artifact

uses: actions/[email protected]

Learn more about this action in actions/upload-pages-artifact

Choose a version

upload-pages-artifact

A composite Action for packaging and uploading artifact that can be deployed to GitHub Pages.

Usage

See action.yml

Artifact validation

While choosing to use this action as part of your approach to deploying to GitHub Pages is technically optional, we highly recommend it since it takes care of producing (mostly) valid artifacts.

However, if you do not choose to use this action but still want to deploy to Pages using an Actions workflow, then you must upload an Actions artifact that meets the following criteria:

The tar file must:

  • be under 10GB in size (we recommend under 1 GB!)
    • ⚠️ The GitHub Pages officially supported maximum size limit is 1GB, so the subsequent deployment of larger tarballs are not guaranteed to succeed — often because they are more prone to exceeding the maximum deployment timeout of 10 minutes.
    • ⛔ However, there is also an unofficial absolute maximum size limit of 10GB, which Pages will not even attempt to deploy.
  • not contain any symbolic or hard links
  • contain only files and directories

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. Publish the draft release from the main branch with semantic version as the tag name, with the checkbox to publish to the GitHub Marketplace checked. ☑️

  3. After publishing the release, the release workflow will automatically run to create/update the corresponding the major version tag such as v0.

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

License

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