Generated from
folio-assistant-core/collab/processes/content/content-change-review-publish.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Merge and publish a content change
Process_ContentChangeReviewPublish · strict (defaulted) · 4 step(s)
Merging an approved content change on the owner’s explicit confirmation and publishing it: remove the staging preview, rebuild the main site and watch it. A change that is not merged keeps its preview.
Called from content-change-review after the committee approves. Approving is the committee’s judgement and merging is a separate, confirmed act, which is why the merge opens this phase rather than closing the review.
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
Steps
Every one of the 4 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Merge, on explicit confirmationTask_Merge | Review Committee | prepare-merge | The owner says “merge it”, and only then is the branch merged. Merge to main triggers: 1. the main site rebuilds with the changes; 2. the staging preview’s cleanup runs; 3. the review comments committed on the feature branch land on main, as the review record. |
| **Remove branches/ `Task_CleanupStaging` | CI/CD Pipeline | feature-staging | When the PR is merged or closed, the cleanup job removes the branches/<slug>/ directory from gh-pages so stale previews don’t accumulate. |
Rebuild main siteTask_RebuildMain | CI/CD Pipeline | content-publish | docs-site.yml triggers on the merge commit to main, rebuilding the root of gh-pages with the accepted changes. The build SHA stamp now reflects the merged state. |
Note the main-branch watchTask_WatchMainCI | CI/CD Pipeline | watchtodo-manager | Second dispatch point: the change was approved and merged, and the root of the site has been rebuilt from main. A failing main build can look like a green run from inside the repo. note rather than claim: the branch-watch bean already exists, andwhether the publish SUCCEEDED is not this step’s judgement (the build reports its own exit code). A bean is not closed on someone else’s say-so, so the step records what it observed and leaves the verdict to the watcher. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
PR merged?GW_Merged | Was the PR merged? Yes removes the branches/<slug>/ preview; No ends this run at End_NotMerged without deploying and without looping back into review (the lane note says why); the preview stays in place, and the next push starts a new run. | Yes → Remove branches/ **No** → Not merged: preview kept |