Welcome to LeviFREE's Blog

Goal#

1. Validate basic Markdown specifications.
2. Check the availability of internal links.
3. Execute a Jekyll build to ensure it’s publishable.

1. Create a New Workflow#

Create .github/workflows/blog-quality.yml:

1
name: Blog Quality
2

3
on:
4
  push:
5
    branches: ["master", "main"]
6
  pull_request:
7

8
jobs:
9
  check:
10
    runs-on: ubuntu-latest
11

12
    steps:
13
      - name: Checkout
14
        uses: actions/checkout@v4
15

16
      - name: Setup Ruby
17
        uses: ruby/setup-ruby@v1
18
        with:
19
          bundler-cache: true
20

21
      - name: Install Node
22
        uses: actions/setup-node@v4
23
        with:
24
          node-version: "20"
25

26
      - name: Install markdownlint
27
        run: npm i -g markdownlint-cli
28

29
      - name: Lint markdown
30
        run: markdownlint "**/*.md" --ignore node_modules
31

32
      - name: Build Jekyll
33
        run: bundle exec jekyll build

2. Dead Link Checking (Optional but Recommended)#

You can add lychee:

1
      - name: Link check
2
        uses: lycheeverse/lychee-action@v2
3
        with:
4
          args: --verbose --no-progress "./**/*.md" "./_site/**/*.html"

If you have many external links, it is recommended to whitelist domains that occasionally timeout to avoid false positives.

3. Branch Protection#

Enable Branch Protection in the repository settings:

• Require PRs to pass Blog Quality.
• Forbid direct pushes to the main branch.

This step significantly reduces the probability of “accidentally pushing broken content to production.”

Common Errors and Troubleshooting#

1. bundler: command not found: jekyll: Gem dependencies aren’t fully installed. Run bundle install first.
2. Front Matter syntax error: Check if --- is paired and if indentation is consistent.
3. False positive dead links: Verify locally with curl -I first, then add them to the ignore list.

Summary#

The key to a high-quality blog isn’t writing fast, but ensuring “every release is stable.” Once you set up CI, you can focus your energy on content instead of production troubleshooting.