Documentation
¶
Overview ¶
Command scaffold-sync propagates the pinned action refs in the committed release workflows back into the scaffold templates they were rendered from, keeping TestSelfScaffoldParity satisfied after a dependency bump.
It exists because the parity is one-directional in practice. Dependabot's github-actions ecosystem discovers `.github/workflows/*` and composite action manifests only — no ecosystem scans a .tmpl under internal/ — so every action bump it opens lands on the rendered workflow alone, breaks parity, and can never go green on its own (iss-209). This command is the other half of that loop, run by hand via `make scaffold-sync`. Nothing in CI invokes it: the drift is gated by TestSelfScaffoldParity and TestSyncRepoPinsIsCleanToday under preflight, and zero-touch propagation onto the dependabot branch is a recorded dead end (a workflow_run implementation was built and rejected in review — see iss-209).
Re-rendering the template over the workflow would REVERT the bump and turn a red PR into a silently useless green one, so the flow is one-way by design.
Exit codes: 0 nothing to do (or, with no -check, the sync was applied); 1 a fault; 3 with -check, templates are out of date and nothing was written.
Source Files