Skip to main content
This feature is experimental. Flags, output shape, and behavior may change between releases. Use in controlled workflows and pin versions in CI.Conflict handling and sync contracts may evolve as TMS integrations mature.

​
Usage

hyperlocalise sync pull [--config <path>] [flags]

​
Safe default behavior

sync pull defaults to dry-run mode. Start by reviewing the report, then rerun with --dry-run=false. sync pull treats the remote adapter as authoritative at execution time. It fetches a fresh remote snapshot for the requested scope, compares it to local files, and then applies pull policy and invariant checks before writing local updates. Local metadata sidecars can still be used for reporting, but they are not required for pull correctness.

​
Flags

  • --config: config path
  • --locale: target locale(s), repeatable
  • --key-prefix: limit sync scope to keys with any matching prefix, repeatable
  • --dry-run: preview only (default true)
  • --output: text, json, or markdown
  • --fail-on-conflict: return error when conflicts are detected (default true)
  • --apply-curated-over-draft: allow curated remote values to replace local draft values (default true)

​
Example

hyperlocalise sync pull --locale es-ES --output json

hyperlocalise sync pull --locale es-ES --key-prefix checkout. --output json

​
Notes

  • remote reads are always fresh for the requested scope
  • pull applies entry-level creates and updates after policy checks
  • invariant violations still block unsafe local writes
See conflict handling for resolution strategy.

​
See also