Overhaul document review and draft publication workflows - #138
Merged
Merged
Conversation
AdamGohs
had a problem deploying
to
review-control
September 9, 2026 15:24 — with 
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being deployed
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.
Description
Allow new documents to merge and deploy as active drafts after content review, with Director review initiated separately. The Director uses a stable preview and full-document inline review PR; approval or administrator waiver creates a linked publication PR containing corrections and the selected draft-flag reversal. An administrator verifies and merges publication, then approves production deployment.
Unify all review lanes around administrator classification, one authoritative reviewer per stage, durable completion, explicit restart/waiver actions, and administrator role flexibility. Add protected review state, deduplicated handoffs, preview recovery/cleanup, main-only production, and updated author/reviewer guidance. Document attribution remains manual; no automatic reminders or separate notification infrastructure are added.
Document scope
Administrator infrastructure overhaul spanning GitHub workflows, review scripts, authoring helpers, the Documentation Guide, and GitHub workflow guidance. This is the implementation cutover, not a routine single-document author PR.
Validation
Review notes
Activation requires a dedicated GitHub App, credentials in a main-only protected review-control environment, controller branch protections, required statuses bound to the App, and production environment restrictions. Follow the activation checklist. These settings have not been applied, and live end-to-end behavior has not been verified. No pilot, migration, merge, or deployment was performed.
GitHub users' native subscriptions and email preferences still control notifications from their own review conversations; the controller reduces its own automated notifications.