Conversation
Use pull_request_target with a two-job split so untrusted PR code never has access to write permissions. The build job checks out the PR with read-only permissions, and the deploy job only runs trusted code from main. Composite actions are referenced from @main to prevent PR code from replacing build/deploy scripts. The override_site_url.py script is moved into the build-docs action directory and referenced via github.action_path for the same reason. Co-Authored-By: Claude Opus 4.6 (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.
Summary
pull_requesttopull_request_targetso fork PRs get write permissions for deploying previews@maininstead of./to prevent PR code from replacing build/deploy scriptsoverride_site_url.pyinto thebuild-docsaction directory and reference viagithub.action_pathfor the same reasonTest plan
docs.ymlanddocs-release.ymlworkflows are unaffected (they use local./action refs, which are compatible with thegithub.action_pathchange)🤖 Generated with Claude Code