Add CI for `jekyll build`

Open
  • Is something wrong?
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
jekyll
Domain
build-system, ci-cd

Research direction

Start by checking how this GitHub Pages site currently builds and deploys, then identify the existing Jekyll build entry point. Add CI coverage that runs the Jekyll build before deployment, and verify that the check succeeds for the website.

Written by the indexing model from the issue text.

Description

This ensures the website can actually deploy before deploying it

Dominant language
CSS
Stars
10
Forks
11
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rust-GCC/Rust-GCC.github.io

All issues in Rust-GCC/Rust-GCC.github.io

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.