Document active static publishing and the contributor entry points - #38
Merged
ClaudiuSchuster merged 1 commit intoSep 8, 2026
Merged
Conversation
ClaudiuSchuster
marked this pull request as ready for review
September 8, 2026 14:24
ClaudiuSchuster
deleted the
oss-oo/static-publication-active-60f8-20260908
branch
September 8, 2026 14:25
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.
Static publication is now configured and enabled after a canonical Actions pilot, retained rollback exercise and verified republication. Update the repository's entry points and operations guides so contributors can tell which changes publish automatically and which still require separate Commons or server-policy work.
The public agent guide gains direct links to the documentation map and contribution workflow. Full-check prerequisites now include OpenSSH's key parser. Worker and database promotion remain explicit separate stages.
Validation: complete repository checks, the canonical publication and rollback evidence linked from the publication guide, and an independently verified production target. This merge will also exercise the enabled post-merge workflow with the updated public agent guide.