[codex] Harden site workflows and template escaping#16
Merged
systemreliability merged 4 commits intoMay 2, 2026
Conversation
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
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
This draft PR hardens the site build/deploy path and a couple of template surfaces found during the code review.
contents: read, while deployment-only runs getcontents: write.fjogeleit/yaml-update-action@mainand replaced it with a local Ruby one-liner in the deploy-only job.jsonifybefore embedding them into the JSON script block.How to check
.github/workflows/deploy.yml_layouts/distill.liquid_includes/head.liquid_pages/publications.mdDeploy site / buildworkflow on the pull request._layouts/distill.liquidand verify the generated JSON values now usejsonify.Deploy site / deployworkflow. It should build and deploy normally.Final merge path
main.Notes
This intentionally does not change the broader al-folio templates or content data. It focuses on the review findings with the largest risk surface: PR token permissions, mutable workflow action refs, JSON escaping in Distill front matter, and duplicate protocol-relative PlumX script loading.