obsidian-propagate

Sync boiler-template updates by running the propagate workflow, which pushes shared changes to all downstream plugins configured in the sync targets file. It ensures tooling consistency across the ecosystem.

Drift detection identifies when downstream plugins diverge from the shared boiler-template. The propagate workflow runs drift checks across managed targets to ensure files and workflows remain aligned with the central template.

Yes, you can run a dry-run to preview boiler-template synchronization changes. This shows exactly what files and rendered workflows will be updated across downstream plugins before committing to a sync.

Exclude specific plugins by defining per-plugin opt-outs in the targets configuration file. The sync workflow respects these settings, ensuring excluded plugins do not receive shared tooling or file updates.

Yes, propagation relies on a per-target boiler configuration file to render workflows and a central sync script. These dictate how shared files are propagated and how CI/Release workflows are generated for each target.