gat sync

Usage: gat sync [OPTIONS]

Options:
  -o, --full-output
          Show all rows and complete details

      --selection <NAME>
          Use this saved selection for this operation without changing the
          default

      --path <PATH>
          Select this file or subtree. Any explicit --path, --include, or
          --exclude replaces the complete configured selection. Use --path . for
          the whole repository. For mount add, omission selects the source root;
          repository selection defaults never apply to mounts

      --include <INCLUDE>
          Glob pattern (matched relative to `--path`) selecting which paths to
          include. Repeatable. Component-aware: `*.bin` matches only immediate
          children, while `**/*.bin` matches recursively. Empty means everything
          under `--path`

      --exclude <EXCLUDE>
          Glob pattern (matched relative to `--path`) excluded from `--include`
          (or from everything under `--path`, if `--include` is empty).
          Repeatable. Component-aware like `--include`; exclude always wins over
          include

      --force
          Overwrite or remove locally modified gat-managed files instead of
          leaving them untouched as conflicts

      --dry-run
          Show what would be materialized, replaced, removed, or flagged as a
          conflict/missing object, without changing anything

      --trust-state
          Trust `gat.lock` plus recorded materialized state without touching the
          working tree. This opts into the fast path; by default `gat sync`
          validates with Git-style lazy stat-then-hash fallback

      --fetch
          Fetch missing cache objects from the remote before reconciling, like
          `gat pull` does, instead of `gat sync`'s normal local-cache-only
          behavior. Same as `gat config sync.auto_fetch true`, for one run

      --repair
          Re-fetch and re-materialize any cache object found corrupted during
          this sync (a conflict where the cache object gat would have used is
          itself bad, not just the working file) from a remote, instead of only
          reporting it

      --remote <REMOTE>
          Remote to fetch missing/repair corrupted cache objects from. Overrides
          path routing; when omitted, routes choose storage by path, with the
          configured default remote as fallback. Only meaningful with
          `--fetch`/`--repair` (or `sync.auto_fetch`/ `sync.auto_repair`)

      --rematerialize
          Recreate already-correct managed files using the current
          `cache.materialization_strategy`, even though their content is already
          up to date. Unlike a plain `gat sync` (which leaves an already-correct
          file untouched no matter how `cache.materialization_strategy`
          changed), this may rewrite a large amount of working-tree data: every
          selected clean file is recreated. Forces full working-tree validation
          for this run (bypassing `sync.trust_state`'s fast path) so a locally
          modified file is reported as a conflict instead of silently
          overwritten; combine with `--force` to overwrite it anyway. Combinable
          with `--dry-run` to preview what would be recreated

  -h, --help
          Print help (see a summary with '-h')