Add GitHub Actions Jekyll build + deploy workflow (#98)#104
Merged
Conversation
Replace the default branch-based GitHub Pages build with an Actions workflow that runs `bundle exec jekyll build` on a clean runner and publishes _site/ via actions/deploy-pages. Keeps the github-pages gem so the built output matches the current site, while unlocking custom plugins, build-time code inlining, and content lint/test gates. Document the new pipeline (and the required Settings -> Pages source switch) in website-dev.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
Author
|
Switched it to 
|
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
Spikes the GitHub Actions Jekyll deploy from #98 — the V2.0 enabler that unblocks custom plugins (#101), build-time code inlining (#100), and content lint/test gates (#99).
Adds
.github/workflows/jekyll.yml: on every push tomain(and manual dispatch) it runsbundle exec jekyll buildon a clean Ubuntu runner and publishes_site/viaactions/deploy-pages. It still installs the existinggithub-pagesgem from theGemfile, so the built output matches the current branch-based build — this is a no-regret swap of the build mechanism, not the site.Verification
bundle exec jekyll buildpasses;remote_themeresolves,baseurl: /physcomphandled byconfigure-pages(base_path=/physcomp).website-dev.md.Cutover (after merge)
The Actions deploy only takes over publishing once Settings → Pages → Build and deployment → Source is switched from "Deploy from a branch" to GitHub Actions. Until then the legacy build keeps serving and the workflow's deploy step is a no-op. Once merged, I'll flip the Pages source (per our agreed plan) and confirm the first green production deploy.
Closes #98 once the source switch is confirmed live.
🤖 Generated with Claude Code