私有化 Git Pages 源码仓库

# This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by
# separate terms of service, privacy policy, and support
# documentation.

# Sample workflow for building and deploying a Jekyll site to GitHub Pages
name: Deploy Jekyll site to Pages

on:
  # Runs on pushes targeting the default branch
  push:
    branches: ["YOUR_PRIVATE_REPO_SOURCE_BRANCH"]

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

env:
  TZ: Asia/Shanghai

jobs:
  # Build job
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
           persist-credentials: true # false 是用 personal token，true 是使用 GitHub token
           fetch-depth: 0
      - name: Setup Ruby
        uses: ruby/setup-ruby@55283cc23133118229fd3f97f9336ee23a179fcf # v1.146.0
        with:
          ruby-version: '3.1' # Not needed with a .ruby-version file
          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
          cache-version: 0 # Increment this number if you need to re-download cached gems
      - name: Build with Jekyll
        # Outputs to the './_site' directory by default
        run: bundle exec jekyll build --baseurl "$" --config ./_config.yml
        env:
          JEKYLL_ENV: production
          TZ: Asia/Shanghai
      - name: Upload artifact
        # Automatically uploads an artifact from the './_site' directory by default
        uses: actions/upload-pages-artifact@v1
      - name: Set SSH Environment
        env:
          # 1. Add this private key and title as DEPLOY_KEY in this repo -> settings/secrets
          # 2. Add corresponding public key and named as any text to the github page repo -> settings/deploy keys
          DEPLOY_KEY: $
          USER_NAME: YOUR_USER_NAME
          USER_EMAIL: YOUR_USER_EMAIL
        run: |
          mkdir -p ~/.ssh/
          echo "$DEPLOY_KEY" | tr -d '\r' > ~/.ssh/id_rsa
          chmod 600 ~/.ssh/id_rsa
          chmod 700 ~/.ssh && chmod 600 ~/.ssh/*
          ssh-keyscan github.com >> ~/.ssh/known_hosts
          git config --global user.name $USER_NAME
          git config --global user.email $USER_EMAIL
      - name: Commit and Push to Git Pages
        env:
          USER_NAME: YOUR_USER_NAME
          USER_EMAIL: YOUR_USER_EMAIL
        working-directory: ./
        run: |
          git clone -b PUBLIC_REPOSITORY_BRANCH git@github.com:YOUR_USER_NAME/YOUR_USER_NAME.github.io.git gitpage_repo
          cd gitpage_repo
          cp robots.txt ../_site/robots.txt
          rm -rf *
          cp -r ../_site/* .
          git add -A
          git -c user.name="$USER_NAME" -c user.email="$USER_EMAIL" commit -am "Site Updated: `date +'%Y-%m-%d %H:%M:%S'`"
          git push origin master -f -q