Repository navigation
ci: declare website publication baseline - #5
Merged
Merged
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
1 participant
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.
Declare the website's stable source-policy and Pages validation checks for its signed initial publication. Its previously empty repository receives the Apache-2.0 licensed site, the standard master branch and merge settings, read-only workflow-token defaults, and both active rulesets. Pages deploys through the reviewed Actions workflow.
The initial source is signed and passes source/content checks. Existing local website validation passed 20 pipeline tests, 6 documentation sites and 398,845 internal links. Initial publication retains that compilation evidence; the first hosted deployment supplies the public URL acceptance. No administrator bypass or required-check removal is used.