FoliageSample/.github/workflows/GenerateViaLocalBuild.yml at main · pillar-markup/FoliageSample · GitHub

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
name: GenerateViaLocalBuild

# Controls when the workflow will run
on:
  # Triggers the workflow on push or pull request events but only for the "main" branch
  push:
    branches: [ "main" ]
    # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: macos-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v4

      - name: Build Foliage
        run: |
           git clone https://github.com/pillar-markup/foliage.git
           ./foliage/scripts/build.sh

      - name: Execute Foliage
        run: |
           ./build/foliage --source site --target generated

      - uses: actions/upload-artifact@v5
        with:
            name: foliage-generated
            path: generated

      - name: AddNoJekill
        run: touch generated/.nojekyll

  deploy:
    runs-on: ubuntu-latest
    needs: [build]

    steps:
    # needed by JamesIves/github-pages-deploy-action
    - uses: actions/checkout@v4

    - uses: actions/download-artifact@v5
      with:
        path: generated

    - name: debug
      run: ls -R

    - name: deploy
      uses: JamesIves/github-pages-deploy-action@v4.4.1
      with:
        branch: gh_pages # The branch the action should deploy to.
        folder: generated # The folder the action should deploy.
      if: github.event_name != 'pull_request'