dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use latest Jekyll-action configuration (#8579) 

Merge pull request 8579
This commit is contained in:
Jonathan Darrer 2021-03-27 16:26:59 +00:00 committed by GitHub
parent dfc65090ea
commit 91c0f2a08d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/_docs/continuous-integration/github-actions.md
View File

@ -113,9 +113,9 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/checkout@v2 - uses: actions/checkout@v2
- uses: helaili/jekyll-action@2.0.5 - uses: helaili/jekyll-action@v2
env: with:
JEKYLL_PAT: ${{ secrets.JEKYLL_PAT }} token: ${{ secrets.GITHUB_TOKEN }}
``` ```
{% endraw %} {% endraw %}
@ -128,7 +128,7 @@ The above workflow can be explained as the following:
- The **checkout** action takes care of cloning your repository. - The **checkout** action takes care of cloning your repository.
- We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.5`. - We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.5`.
This handles the build and deploy. This handles the build and deploy.
- We set a reference to a secret **environment variable** for the action to use. The `JEKYLL_PAT` - We set a reference to a secret **environment variable** for the action to use. The `GITHUB_TOKEN`
is a _Personal Access Token_ and is detailed in the next section. is a _Personal Access Token_ and is detailed in the next section.
Instead of using the **on.push** condition, you could trigger your build on a **schedule** by Instead of using the **on.push** condition, you could trigger your build on a **schedule** by
@ -159,7 +159,7 @@ build using _Secrets_:
to commit to the `gh-pages` branch. to commit to the `gh-pages` branch.
3. **Copy** the token value. 3. **Copy** the token value.
4. Go to your repository's **Settings** and then the **Secrets** tab. 4. Go to your repository's **Settings** and then the **Secrets** tab.
5. **Create** a token named `JEKYLL_PAT` (_important_). Give it a value using the value copied 5. **Create** a token named `GITHUB_TOKEN` (_important_). Give it a value using the value copied
above. above.
### Build and deploy ### Build and deploy