🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
Go to file
James Ives e58ef6c702
Action Badges 🚀
Adds badges to the action readme.
2019-03-03 12:14:19 -05:00
.github Init 🚀 2019-03-02 18:43:28 -05:00
Dockerfile Valid color for the marketplace 2019-03-03 12:02:39 -05:00
entrypoint.sh Update entrypoint.sh 2019-03-03 12:10:31 -05:00
LICENSE Initial commit 2019-03-02 11:04:50 -05:00
README.md Action Badges 🚀 2019-03-03 12:14:19 -05:00
screenshot.png Update screenshot.png 2019-03-03 12:01:09 -05:00

Github Pages Deploy Action 🚀

View Action Issues

This Github action will handle the building and deploying process of your project to Github Pages. It can be configured to upload your production ready code into any branch you'd like, including gh-pages and docs.

Getting Started ✈️

Before you get started you must first create a fresh branch where the action will deploy the files to. You can replace gh-pages with whatever branch you'd like to use in the example below.

git checkout --orphan gh-pages
git rm -rf .
touch README.md
git add README.md
git commit -m 'Initial gh-pages commit'
git push origin gh-pages

Once setup you can then include the action in your workflow to trigger on any event that Github actions supports.

action "Deploy to Github Pages" {
  uses = "JamesIves/github-pages-deploy-action@master"
  env = {
    BUILD_SCRIPT = "npm install && npm run-script build"
    BRANCH = "gh-pages"
    FOLDER = "build"
    COMMIT_EMAIL = "github-pages-deployer@jives.dev"
    COMMIT_NAME = "Github Pages Deployer"
  }
  secrets = ["GITHUB_TOKEN"]
}

Configuration 📁

The env portion of the workflow must be configured before the action will work. Below you'll find a description of what each one does.

Key Value Information Required
BUILD_SCRIPT If you require a build script to compile your code prior to pushing it you can add the script here. The Docker container which powers the action runs Node which means npm commands are valid. If you're using a static site generator such as Jekyll I'd suggest building the code prior to pushing it to your base branch. No
BRANCH This is the branch you wish to deploy to, for example gh-pages or docs. Yes
BASE_BRANCH The base branch of your repository which you'd like to checkout prior to deploying. This defaults to master. No
FOLDER The folder in your repository that you want to deploy. If your build script compiles into a directory named build you'd put it here. Yes
COMMIT_NAME Used to sign the commit, this should be your name. Defaults to gh-pages-deploy@jives.dev No
COMMIT_EMAIL Used to sign the commit, this should be your email. Defaults to Github Pages Deployer No

Example