Fix the docs workflow's Jekyll output permissions - #34
Merged
Conversation
actions/jekyll-build-pages runs in a container as root, so _site comes back owned by root and the step that drops the API reference into it failed with "Permission denied". The workflow also only ran on the default branch, which meant a site that no longer builds could only be discovered after merging. It now builds on pull requests too, and deploys only when the event is not one. Co-Authored-By: Claude Opus 5 (1M context) <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
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.
The first Docs run after #33 failed:
actions/jekyll-build-pagesruns in a container as root, so_sitecomes back owned by root and the step that drops the API reference into it cannot write there. The step now takes ownership first.The workflow also only ran on the default branch, so a site that no longer builds could only be discovered after merging — which is exactly what happened here. It now builds on pull requests too and deploys only when the event is not one, so this PR's own Docs run validates the fix.
Folded into the v0.6.4 release.
🤖 Generated with Claude Code