Skip to content

Commit 91c0f2a

Browse files
authored
Use latest Jekyll-action configuration (#8579)
Merge pull request 8579
1 parent dfc6509 commit 91c0f2a

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

docs/_docs/continuous-integration/github-actions.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -113,9 +113,9 @@ jobs:
113113
runs-on: ubuntu-latest
114114
steps:
115115
- uses: actions/checkout@v2
116-
- uses: helaili/jekyll-action@2.0.5
117-
env:
118-
JEKYLL_PAT: ${{ secrets.JEKYLL_PAT }}
116+
- uses: helaili/jekyll-action@v2
117+
with:
118+
token: ${{ secrets.GITHUB_TOKEN }}
119119
```
120120
121121
{% endraw %}
@@ -128,7 +128,7 @@ The above workflow can be explained as the following:
128128
- The **checkout** action takes care of cloning your repository.
129129
- We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.5`.
130130
This handles the build and deploy.
131-
- We set a reference to a secret **environment variable** for the action to use. The `JEKYLL_PAT`
131+
- We set a reference to a secret **environment variable** for the action to use. The `GITHUB_TOKEN`
132132
is a _Personal Access Token_ and is detailed in the next section.
133133

134134
Instead of using the **on.push** condition, you could trigger your build on a **schedule** by
@@ -159,7 +159,7 @@ build using _Secrets_:
159159
to commit to the `gh-pages` branch.
160160
3. **Copy** the token value.
161161
4. Go to your repository's **Settings** and then the **Secrets** tab.
162-
5. **Create** a token named `JEKYLL_PAT` (_important_). Give it a value using the value copied
162+
5. **Create** a token named `GITHUB_TOKEN` (_important_). Give it a value using the value copied
163163
above.
164164

165165
### Build and deploy

0 commit comments

Comments
 (0)