Refine overwrite options #663
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is this PR?
Why is this PR needed?
The existing
alwaysoverwrite option was misleading because it did notactually force overwriting files. By default, rclone only copies files when
timestamps or checksums differ, which caused confusion for users.
This PR clarifies the overwrite behavior and aligns it with rclone semantics.
What does this PR do?
This PR refines overwrite behavior for transfers by:
if_differentoption that uses rclone’s default behavioralwaysto use--ignore-timesso it truly overwrites filesneverandif_source_newerunchangedReferences
Closes #624
How has this PR been tested?
This change affects argument construction only.
The logic was verified by inspecting the generated rclone arguments and ensuring
they match the expected rclone flags.
No runtime behavior or external dependencies were modified.
Is this a breaking change?
No.
This change clarifies behavior but does not remove or rename any existing options.
Does this PR require an update to the documentation?
Yes — documentation updated in
transfer-data.md.Checklist