Skip to main content
Sync connects your repository ledger to one hosted project. Follow CLI connection first. Your local declarations and notes stay under your control; the cloud supplies observations and event history.

​
Review what will cross the connection

The dry run reports the planned upload without network work. Pull-only retrieves cloud history. Review the default selection before pushing expectations. Wanted placements require --include-wanted when you intend to include them.
Use --push-only when you intend to upload expectations without pulling feeds. Keep your saved connection tied to the same workspace and project. For a different identity, prepare a separate ledger so existing mappings cannot attach to another account.

​
Recover an interrupted pull

Source and destination feeds use separate cursors. Sync applies each page before advancing its cursor, and replay deduplicates events. An expired cursor triggers snapshot recovery. Inspect the reported recovery outcome; a gap means some event history is no longer retained. After a network failure, rerun the same intended sync. For authentication or identity refusal, correct the connection first. Keep local notes and tags intact while resolving cloud access. Do not delete cursors merely to silence an error.

​
Export a reviewable report

Read the ledger guide before sharing report files, especially if you include notes. For cloud recovery, export_link_watches supplies paginated monitored records. Follow every returned cursor to export the selected dataset; one page is not a complete export. Use get_link_evidence or get_target_evidence for retained observation snapshots. Expired raw evidence leaves metadata available, but a fresh check cannot reproduce an old page. See evidence, webhooks and troubleshooting.