mirrors/90DaysOfDevOps
1
0
Fork 0
mirror of https://github.com/MichaelCade/90DaysOfDevOps.git synced 2024-12-22 22:23:14 +07:00
Code Issues Packages Projects Releases Wiki Activity

Fix Liquid error: Liquid variables are disabled

Browse Source
This commit is contained in:
Michael Cade 2022-04-08 14:25:50 +01:00
parent 34a5939bce
commit 7376ccb2be
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/deploy-blog-posts.yml vendored
View File

@ -36,7 +36,7 @@ jobs:
# See https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
github_token: ${{ secrets.GITHUB_TOKEN }}
# (Optional) The files to publish. Default is "posts/**/*.md"
files: 'Days/**/day75.md'
files: 'Days/**/*.md'
# (Optional) The git branch to use. Default is 'main'.
branch: main
# (Optional) Use conventional commit messages. Default is false.

4
Days/day75.md
View File

@ -6,8 +6,6 @@ tags: "devops, 90daysofdevops, learning"
cover_image: null
canonical_url: null
---
## GitHub Actions Overview
In this section I wanted to move on and take a look at maybe a different approach to what we just spent time on. GitHub Actions is where we will focus on in this session.
@ -118,7 +116,7 @@ You can see from the above that for one of our steps we have an action called gi
Also in the code snippet above it mentions GITHUB_TOKEN so I was interested to find out why and what this does and needed for.
"NOTE: If you pass the Environment variable GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} in your workflow, then the GitHub Super-Linter will mark the status of each individual linter run in the Checks section of a pull request. Without this you will only see the overall status of the full run. **There is no need to set the GitHub Secret as it is automatically set by GitHub, it only needs to be passed to the action.**"
"NOTE: If you pass the Environment variable `GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}` in your workflow, then the GitHub Super-Linter will mark the status of each individual linter run in the Checks section of a pull request. Without this you will only see the overall status of the full run. **There is no need to set the GitHub Secret as it is automatically set by GitHub, it only needs to be passed to the action.**"
The bold text being important to note at this stage. We are using it but we do not need to set any environment variable within our repository.