-
Notifications
You must be signed in to change notification settings - Fork 3
50 lines (45 loc) · 1.67 KB
/
Copy pathdeploy-web.yml
File metadata and controls
50 lines (45 loc) · 1.67 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
name: Deploy web showcase to GitHub Pages
# Publishes the static showcase site under `web/` to GitHub Pages via
# GitHub Actions. The site is plain HTML / CSS / JS + generated showcase
# assets — no build step. It replaced the old "deploy from branch /docs"
# setup when the showcase moved out of docs/ into web/ so that docs/ holds
# documentation only.
#
# REQUIRES: repository Settings → Pages → Source = "GitHub Actions"
# (one-time switch from "Deploy from a branch"). Until that switch is made,
# this workflow builds the artifact but Pages keeps serving the old source.
#
# Triggers: every push to `main` AND every `v*` release tag. The tag trigger
# is the reliable one for releases — the v1.8.0 release fast-forwarded `main`
# with 67 changed `web/` files yet the old `paths: web/**` filter silently
# skipped the deploy, so the live site kept serving the previous release. We
# dropped the paths filter rather than depend on it: `main` is only pushed at
# releases / hotfixes, so deploying unconditionally is cheap and correct, and
# the `v*` tag is a second guaranteed trigger. `concurrency` de-dupes the two
# triggers a release fires.
on:
push:
branches: [main]
tags: ["v*"]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: pages
cancel-in-progress: true
jobs:
deploy:
runs-on: ubuntu-latest
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- uses: actions/checkout@v6
- uses: actions/configure-pages@v6
- uses: actions/upload-pages-artifact@v5
with:
path: web
- id: deployment
uses: actions/deploy-pages@v5