Building the site with a CI


Make sure environment variables contain JEKYLL_ENV=production.

Private key

Private keys can be provided as secrets by your CI, but they need to be files accessible to jekyll. You can use temporary files.

Permanent store

Notifications are tracked via a permanent store in _data/activity_pub.yml. You’ll need to commit and push changes to this file after running the CI.

If you use the jekyll-write-and-commit-changes plugin, the commit will be done automatically, but git push needs to be run separately.


After jekyll build and whatever steps you need to publish your site, run jekyll notify --key /path/to/private.key.

bundle exec jekyll build --key /path/to/private.key
# push _site somewhere and wait for propagation
bundle exec jekyll notify --key /path/to/private.key