-
Notifications
You must be signed in to change notification settings - Fork 78
70 lines (59 loc) · 1.76 KB
/
Copy pathjekyll.yml
File metadata and controls
70 lines (59 loc) · 1.76 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
name: Deploy Jekyll site to Pages
on:
push:
branches: ["main"]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v7
- name: Setup Ruby
uses: ruby/setup-ruby@v1
with:
ruby-version: '3.3'
bundler-cache: true
working-directory: ./docs
- name: Setup Pages
id: pages
uses: actions/configure-pages@v6
- name: Build with Jekyll
run: |
cd docs
bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
env:
JEKYLL_ENV: production
- name: Upload artifact
uses: actions/upload-pages-artifact@v5
with:
path: ./docs/_site
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url || steps.deployment-retry.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
# The Pages "syncing_files" backend step fails intermittently with a
# generic "Deployment failed, try again later." GitHub offers no
# server-side retry, so the first attempt is allowed to fail and a second
# attempt runs only when it does. Each call creates a fresh deployment.
- name: Deploy to GitHub Pages
id: deployment
continue-on-error: true
uses: actions/deploy-pages@v5
- name: Wait before retry
if: steps.deployment.outcome == 'failure'
run: sleep 30
- name: Deploy to GitHub Pages (retry)
id: deployment-retry
if: steps.deployment.outcome == 'failure'
uses: actions/deploy-pages@v5