docs: clarify copyto rename behavior#9538
Merged
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.
What does this change do?
Clarifies the
copytocommand description using the wording suggested in the issue: copying a single file to a destination with a different name, for example uploading and renaming in one step.Linked issue
Fixes #9527
For new or changed backends
Not a backend change.
Checklist
test_allpasses for this backend and I can provide a test account for the integration tester - see CONTRIBUTING.md.Verification:
gofmt -w cmd/copyto/copyto.gogo test ./cmd/copyto -count=1git diff --check