Skip to content

Defer Lane 1 checkpoint deploy until after technical edit#108

Merged
AdamGohs merged 2 commits intomainfrom
feature/review-workflow-infrastructure
Apr 10, 2026
Merged

Defer Lane 1 checkpoint deploy until after technical edit#108
AdamGohs merged 2 commits intomainfrom
feature/review-workflow-infrastructure

Conversation

@AdamGohs
Copy link
Copy Markdown
Collaborator

Summary

  • Move the Lane 1 checkpoint deploy from "after Lead Civil approval" to "after the technical edit completes." The technical edit reads source MDX directly via `/technical-edit` and posts inline comments on the PR, so no live deploy is needed during that stage. The live site only ever sees the post-tech-edit version of the document.
  • Update the two affected comment templates in .github/workflows/stage-progression.yml: the Lead-Civil-approved comment no longer instructs the admin to deploy; the technical-edit-checkbox-checked comment now instructs the admin to deploy + assign Director.
  • Update both planning documents to match the new flow: Lane 1 overview in planning/01-repo-implementation.md, and the Lane 1 mentions across the future doc-guide chapters in planning/02-documentation-guide-implementation.md (overview, lanes, author, technical edit, and site admin chapters).

Follow-up to #107 — this commit was made after #107 merged, so it ships separately rather than as part of the original infrastructure PR.

The Lane 1 checkpoint deploy now happens after the technical edit
completes (when the author checks the PR description checkbox), not
after Lead Civil approval. The technical edit reads source MDX
directly via /technical-edit and posts inline comments on the PR, so
no deploy is required during that stage. The live site only ever sees
the post-tech-edit version of the document, and the Director reviews
the same version that will eventually be merged.

Updates the stage-progression workflow's two relevant comment
templates and the corresponding Lane 1 descriptions in both planning
documents.
@AdamGohs AdamGohs requested a review from a team as a code owner April 10, 2026 20:22
Adds an always-runs ci-build.yml workflow that runs npm run build on
every PR, providing a meaningful required status check that catches
broken builds before merge. Unlike deploy.yml's build job (which only
runs on push to main) and pr-preview.yml (which is path-conditional),
this workflow fires on every PR and is therefore safe to mark as a
required check.

Updates pr-preview.yml to (1) include the head commit SHA in the
success comment so reviewers can verify which commit they are seeing,
and (2) on build failure, append a 'preview is stale' warning to the
sticky comment so reviewers cannot unknowingly click through to
outdated content. If no previous successful preview exists, post a
fresh 'preview build failed' comment instead.

Documents the new workflow in planning/01-repo-implementation.md and
adds an architectural note about which checks are appropriate as
required status checks on main.
@AdamGohs AdamGohs merged commit 7714617 into main Apr 10, 2026
1 check passed
@AdamGohs AdamGohs deleted the feature/review-workflow-infrastructure branch April 10, 2026 20:57
@AdamGohs AdamGohs restored the feature/review-workflow-infrastructure branch April 10, 2026 20:58
@AdamGohs AdamGohs deleted the feature/review-workflow-infrastructure branch April 10, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant