-
Notifications
You must be signed in to change notification settings - Fork 1
73 lines (62 loc) · 1.92 KB
/
Copy pathpages.yml
File metadata and controls
73 lines (62 loc) · 1.92 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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
name: Deploy splash to GitHub Pages
on:
push:
# The augment-it rebuild currently lives on `rebuild/turbo-rsbuild` — that's
# where splash/ exists, so that's what we deploy from. `main` is kept for
# after the rebuild lands there. (master/development are intentionally NOT
# watched yet: they have no splash/, so a push would just fail the build.)
branches: [rebuild/turbo-rsbuild, main]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: pages
cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-latest
defaults:
run:
working-directory: splash
steps:
- name: Checkout
uses: actions/checkout@v4
with:
# Single-project repo — no submodules to fetch. The splash reads
# ../changelog and ../context-v as plain file IO from the parent
# repo's working tree.
fetch-depth: 1
- name: Setup pnpm
uses: pnpm/action-setup@v4
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: 22
cache: pnpm
cache-dependency-path: splash/pnpm-lock.yaml
- name: Install
run: pnpm install --frozen-lockfile=false --ignore-workspace
- name: Build
run: pnpm build
- name: Configure Pages
uses: actions/configure-pages@v5
with:
# Auto-enable Pages on first run so the workflow bootstraps itself
# even when "Get Pages site" returns 404 the very first time.
enablement: true
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: splash/dist
deploy:
needs: build
runs-on: ubuntu-latest
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4