Repository navigation
put: skip uploads when destination contents match - #399
Merged
AndreyVMarkelov merged 1 commit intoNov 11, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
put --if-exists skip-same: upload missing files, skip identical files, and return a path conflict when contents differ or the remote content hash is unavailable. Rerunningdbxcli put report.txt /report.txt --if-exists skip-sameskips an unchanged file without transferring its contents.Uses the existing SDK
contenthash.Computeand checks size before hashing. Supports single files, recursive uploads, and stdin; missing destinations use strict add mode to prevent overwriting concurrently created files. Updates JSON help/manifest enums, the public JSON schema, and generated command documentation. Dry-run retains its existing planning behavior without comparing contents. Comparison uses the fetched metadata snapshot and is not atomic with concurrent file changes.Validation:
go test ./...go vet ./...go build ./...Fixes #129.