-
Notifications
You must be signed in to change notification settings - Fork 0
79 lines (66 loc) · 1.97 KB
/
Copy pathpages.yml
File metadata and controls
79 lines (66 loc) · 1.97 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
74
75
76
77
78
79
name: Deploy examples to GitHub Pages
# Builds the Phaser engine at the repo root, then builds the Vite/React
# examples gallery under `examples/` and publishes its `dist/` output to
# GitHub Pages. The gallery is served from
# https://phaserjs.github.io/phas3d/ so we pass `VITE_BASE=/phas3d/` to
# Vite, which rewrites every emitted asset URL with that prefix.
#
# One-time setup required in the repo on GitHub:
# Settings -> Pages -> Build and deployment -> Source: "GitHub Actions"
on:
push:
branches: [main]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
# A single in-flight deploy at a time; new pushes cancel older runs that
# haven't published yet so the latest commit always wins.
concurrency:
group: pages
cancel-in-progress: true
jobs:
build:
name: Build engine + examples
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: 20
cache: npm
cache-dependency-path: |
package-lock.json
examples/package-lock.json
- name: Install root deps
run: npm ci
- name: Build Phaser (produces build/phaser.js)
run: npm run build
- name: Install examples deps
working-directory: examples
run: npm ci
- name: Build examples gallery
working-directory: examples
env:
VITE_BASE: /phas3d/
run: npm run build
- name: Configure Pages
uses: actions/configure-pages@v5
- name: Upload Pages artifact
uses: actions/upload-pages-artifact@v3
with:
path: examples/dist
deploy:
name: Deploy to Pages
needs: build
runs-on: ubuntu-latest
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy
id: deployment
uses: actions/deploy-pages@v4