Add Jekyll build CI workflow#10
Merged
Merged
Conversation
Runs bundle exec jekyll build on every push and PR to main, satisfying the Scorecard CI-Tests check which requires CI to run before merging. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds ruby-version: '3.3' to the workflow and a .ruby-version file for local dev. setup-ruby requires one of these when neither exists. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
v1.99.0 does not know about Ruby 3.3 on ubuntu-24.04. v1.306.0 (latest) includes support for it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the CI-Tests Scorecard check (currently 0/10).
Adds
.github/workflows/build.ymlthat runsbundle exec jekyll buildon every push and PR tomain. This gives Scorecard evidence that CI is running before changes land on the main branch.What it does
pushtomainandpull_requesttargetingmainjekyll buildin production mode — fails the check if the site doesn't build cleanlyExpected score impact
CI-Tests: 0 → 10 (once a few PRs have passed CI)
Note on Branch-Protection and Code-Review
These two Scorecard checks also score 0 and cannot be fixed via a file PR — they require enabling branch protection rules in Settings → Branches on GitHub:
Jekyll buildcheck from this PR)🤖 Generated with Claude Code