Update-Content Phase

Behaviour#

Update-content is where the repository’s own files start to matter. It runs once the workspace content is available, and may run again when that content is refreshed during creation or prebuilding. Because the work is a function of the checked-in files, rerunning it after a content change brings the workspace back in line.

It sits between two easily confused neighbours. On-Create Phase prepares the container before content matters; Post-Create Phase finishes the workspace once everything is in place. Update-content is the step that responds to the content itself.

Examples#

This repository restores its pinned Node tooling here. It uses the lockfile when there is one and falls back to a plain install otherwise:

#!/usr/bin/env bash
set -euo pipefail

if [ -f package-lock.json ]; then
	npm ci
else
	npm install
fi