Generated from
folio-assistant-core/collab/processes/content/content-change-review-stage.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Stage the content change
Process_ContentChangeReviewStage · strict (defaulted) · 4 step(s)
Putting one push of a content change where a person can look at it: build the staging site, deploy it under the branch’s slug, link it on the pull request, and watch the branch’s CI.
Called from content-change-review after the first push and after every revision, so the author and the committee never review a stale preview.
How it connects
- Called by: Content Change and Review
- Calls: none
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
| lane | role | what it does here |
|---|---|---|
| CI/CD Pipeline | build-pipeline | Runs build, stage, comment and watch once per push. |
Steps
Every one of the 4 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Build staging siteTask_BuildStaging | CI/CD Pipeline | feature-staging | feature-staging.yml triggers: 1. Regenerate docs (schema, skills, content-backed pages) 2. Render BPMN diagrams 3. Stamp build with commit SHA + timestamp + branch 4. Build Jekyll site with branches/ baseurl 5. Inject yellow staging banner into every HTML page A draft pull request is staged too, from its first push. A build takes about 22 minutes, and GitHub Pages about 3 to 4 more. |
| **Deploy to branches/ `Task_DeployStaging` | CI/CD Pipeline | feature-staging | The stage job copies the built site into gh-pages under branches/<branch-slug>/, then staging-share.ts apply keeps onlythe files that differ from the live site. The preview’s staging-sw.js serves every other file from the live site and puts the staging banner back on it. Other previews and the main site are left as they are. |
Comment staging URL on PRTask_CommentPR | CI/CD Pipeline | feature-stagingrendered-impact | Bot comments or updates the staging URL on the PR. Includes commit SHA, branch name, and build log link, and the review list of rendered files the change alters (skill rendered-impact), each linked on the preview and on main, with any input the renderer could not place named as not known. |
Open the branch-watch beanTask_WatchBranchCI | CI/CD Pipeline | watchtodo-manager | First dispatch point for a CI watcher: the feature branch has changed and a staging build now exists to watch. The watcher is DISPATCHED BY OPENING A BEAN, not by a workflow_dispatch: this is a task/workflow initiation. A bean makes the watch durable past the session that opened it: the container is reclaimed, and what survives is the bean. Starting the watcher and recording that it is running are ONE declared step, so the two cannot disagree about whether anything is watching. It notes the watch on the bean rather than claiming it: only Process_BeanOpen claims a bean. The note is idempotent, so re-entering on a later push does not duplicate it. |