Conflict resolution

Before starting an offload, Tusk does a preflight check comparing the source files against:

• What's already recorded in the project's file index (the database).
• What's physically present on each destination.
• (When copyLocally is off) what's already in the project's primary folder on your Mac.

When something on the source matches something that already exists, Tusk pauses to ask you what to do. The two main conflict types are described below.

Conflict type 1: file already exists on a destination

The source has a file at a relative path that already exists (in Tusk's index, or physically on disk) on at least one destination. Tusk surfaces a conflict resolution panel listing the conflicting files. Two choices:

• Skip conflicting files: the source files with conflicts are ignored. Everything else proceeds. Use this when the existing destination copies are already correct (you re-inserted the same card by accident, or you're re-running an offload that already mostly finished).
• Overwrite existing files: the source files replace the existing destination copies. Use this when the source is the canonical version (the original on the card; the older destination copy was wrong or stale).

Your choice applies to all conflicts in this offload at once. There's no per-file mixed mode. If you need a mixed approach, run two offloads: one for files to skip, one for files to overwrite, by selecting different source subfolders.

Conflict type 2: file already in your local primary folder

This only applies when copyLocally is off (the offload default). The scenario: you're offloading straight from a card to your destinations, but a file with the same name as a source file is already sitting in your project's primary folder.

Why this matters: if Tusk wrote the source file to the destinations but left a different local file with the same name in the primary folder, the file table would show two conflicting versions of “the same” file. So Tusk asks you to resolve it before starting:

• Delete local copies and continue: removes the conflicting local files via macOS Trash, then offloads the source files to destinations. The destinations (without local copies) become the source of truth for those names. Use this when the source on the card is the canonical version.
• Switch to copy locally: turns the copyLocally toggle on. Now the source files do land in the primary folder, and Tusk handles them via the standard conflict logic above (skip or overwrite).
• Abort: cancel the offload. Resolve the conflict yourself in Finder, then restart.

Conflict type 3: create-project + offload local conflict

During the create-project + offload wizard, the same local-file-conflict scenario can arise: the primary folder you picked already contains files with the same names as source files. Tusk surfaces this inline in the wizard with two choices:

• Skip conflicting files: the offload ignores those names (no overwrite, no deletion).
• Replace with source files: deletes the local copies first, then offloads.

The wizard summary shows your chosen resolution before the offload starts. It's easy to back out of and pick the other option if you change your mind.

Cloud-specific preflight checks

Two extra preflight checks run for Google Drive destinations specifically:

• Storage quota: Tusk checks the available storage on each Google Drive destination before starting. If the source folder is larger than what's available on any of them, the offload is blocked with a clear message naming the destination and the gap.
• Folder collision: Tusk blocks an offload whose target Google Drive folder already contains files from a previous offload (from any source, any project). This prevents two unrelated offloads from sharing a folder. Empty the Drive folder or pick a different one to proceed.