Skip to content

Fix: Ensure --overwrite is respected for checksum matches#1138

Open
YellowRoseCx wants to merge 1 commit intosimulot:developfrom
YellowRoseCx:develop
Open

Fix: Ensure --overwrite is respected for checksum matches#1138
YellowRoseCx wants to merge 1 commit intosimulot:developfrom
YellowRoseCx:develop

Conversation

@YellowRoseCx
Copy link
Copy Markdown

@YellowRoseCx YellowRoseCx commented Oct 19, 2025

Problem:
Previously, if a local asset had the same checksum as a server asset, the upload was immediately skipped as a duplicate (SameOnServer). This happened before the --overwrite flag was ever checked, preventing users from force-replacing a binary-identical file.

Solution:
This PR modifies the ShouldUpload logic to check for the Overwrite flag within the checksum validation block. The order of checks is now:

  1. Is it an in-session duplicate? (Skip)
  2. Is --overwrite enabled? (Force Upload)
  3. Otherwise, it's a server duplicate. (Skip)

This ensures user intent to overwrite is respected while maintaining the efficiency of skipping redundant local uploads.

Resolves issue #1137

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant