Repository navigation
ci: validate documentation inputs before publication - #3
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Documentation used the validator module and dependency lock but only documentation paths triggered a build. Pull requests also had no nonpublishing validation path.
Add those actual inputs to push and PR filters, run PR builds on isolated hosted runners with read-only access, and use the committed lock. Keep Pages setup and publication on trusted main events, with write permissions confined to deployment and the existing serialized deployment group preserved. Pin the existing action versions to exact commits and cancel only superseded PR builds.
Validation: current locked Python 3.11 build and a fresh rebuild both succeeded with the same 9 existing warnings; all 12 generated HTML pages are byte-identical. Actionlint and event/permission checks passed. No source or documentation content changes.