Skip to content

Clarify that pipeline-overrides don't have to be statically used to b… #6

Clarify that pipeline-overrides don't have to be statically used to b…

Clarify that pipeline-overrides don't have to be statically used to b… #6

name: build-validate-publish
# This workflow runs on pull requests and pushes to the main branch, and
# builds/validates the specs, other documents, and supplemental materials.
# This includes verifying the WGSL grammar which is one of the generated
# supplemental materials.
#
# On pushes to the main branch, it also publishes the outputs to GitHub Pages.
on:
pull_request:
paths-ignore: [ "tools/custom-action/Dockerfile" ]
push:
branches: [main]
paths-ignore:
- "tools/custom-action/Dockerfile"
- "tools/custom-action/entrypoint.sh"
# Allows admins to trigger the workflow manually from GitHub's UI.
workflow_dispatch:
jobs:
# Note, spec-prod can publish to gh-pages as well, but we use a custom publish
# step to publish additional files anyway, so we use that instead of making
# many separate gh-pages commits (one per bikeshed file + one for extras).
build-validate-publish:
runs-on: ubuntu-22.04
defaults:
run:
shell: bash
steps:
- uses: actions/checkout@v3
- name: Build and validate with custom action
uses: ./tools/custom-action/
- name: Deploy to GitHub Pages
if: ${{ success() && github.ref == 'refs/heads/main' }}
uses: JamesIves/github-pages-deploy-action@v4.4.2
with:
BRANCH: gh-pages
FOLDER: out