Repository navigation

Make Gemfile.lock authoritative in CI #43

	name: Build and deploy Jekyll site

	on:
	push:
	branches: [main]
	workflow_dispatch:

	permissions:
	contents: read
	pages: write
	id-token: write

	concurrency:
	group: pages
	cancel-in-progress: false

	jobs:
	build:
	runs-on: ubuntu-latest
	steps:
	- name: Checkout
	uses: actions/checkout@v7

	- name: Set up Ruby
	uses: ruby/setup-ruby@v1
	with:
	ruby-version: '3.2.4'
	bundler-cache: true
	env:
	# Fail if Gemfile.lock is out of step with the Gemfile rather than
	# silently re-resolving it, which would deploy gem versions that are
	# not the committed ones. Run `bundle lock` and commit the result.
	BUNDLE_FROZEN: 'true'

	- name: Configure Pages
	uses: actions/configure-pages@v6

	- name: Build site
	run: bundle exec jekyll build
	env:
	JEKYLL_ENV: production

	- name: Upload artifact
	uses: actions/upload-pages-artifact@v5
	with:
	path: _site

	deploy:
	needs: build
	runs-on: ubuntu-latest
	environment:
	name: github-pages
	url: ${{ steps.deployment.outputs.page_url }}
	steps:
	- name: Deploy to GitHub Pages
	id: deployment
	uses: actions/deploy-pages@v5