Generated from folio-assistant-core/collab/processes/content/content-change-review-publish.bpmn by gen-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.

BPMN diagram: Merge and publish a content change

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

lanerolewhat it does here
Review CommitteereviewerMerges only on the owner’s explicit confirmation.
CI/CD Pipelinebuild-pipelineGW_Merged checks whether the approval resulted in a merge; it does not decide whether to approve one, and a “No” ends the run instead of looping back into review.

Steps

Every one of the 4 step(s) is documented.

steplaneskill / sub-processwhat it does
Merge, on explicit confirmation
Task_Merge
Review Committeeprepare-mergeThe 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 Pipelinefeature-stagingWhen 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 site
Task_RebuildMain
CI/CD Pipelinecontent-publishdocs-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 watch
Task_WatchMainCI
CI/CD Pipelinewatch
todo-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, and
whether 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.

decisionwhat decides itbranches
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

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev