Add GitHub Actions workflow to build website via Nuke and Jekyll #4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Build | |
| on: | |
| push: | |
| branches: [ "master" ] | |
| pull_request: | |
| branches: [ "master" ] | |
| jobs: | |
| build: | |
| runs-on: windows-latest | |
| permissions: | |
| contents: read | |
| steps: | |
| - uses: actions/checkout@v4 | |
| with: | |
| fetch-depth: 0 | |
| - name: Run Nuke build | |
| run: .\build.ps1 Default | |
| # The Nuke build and Jekyll build are independent: | |
| # - Nuke compiles the guidelines into standalone HTML documents using Pandoc | |
| # - Jekyll builds the static website from the same source Markdown files | |
| # They share no artifacts and can run in parallel. | |
| jekyll: | |
| runs-on: ubuntu-latest | |
| permissions: | |
| contents: read | |
| steps: | |
| - uses: actions/checkout@v4 | |
| - uses: ruby/setup-ruby@v1 | |
| with: | |
| ruby-version: '3.2' | |
| bundler-cache: true | |
| - name: Build Jekyll site via Nuke | |
| run: ./build.sh JekyllBuild |