Support duplicate handling for Appwrite imports#205
Conversation
Greptile SummaryThis PR adds
Confidence Score: 4/5The logic for skip and overwrite is sound across most resource types; existing open threads on the file/deployment delete-then-upload window and the file overwrite timestamp check are the main remaining concerns before merging. The duplicate-handling plumbing is well-structured and the live-migration validation described in the PR gives reasonable confidence. Two open issues from the previous review round have not been closed: file overwrite always replaces regardless of whether the source is actually newer, and the delete-before-upload window leaves a destination file absent if the upload fails mid-stream. src/Migration/Destinations/Appwrite.php: the importFile overwrite path and importDeploymentWithDuplicateCheck both warrant a second look before merge. Important Files Changed
Reviews (11): Last reviewed commit: "Respect timestamps for binary overwrites" | Re-trigger Greptile |
Summary
Validation
Review Notes