Repository navigation
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.
Recursive copies currently apply
-nonly after the symlink branches. A source link can therefore replace an existing destination file, or overwrite its content when-Lfollows the link, despite no-clobber being requested.Check no-clobber before dispatching recursive entries. Continue merging source directories, including directory links followed with
-L. When copying the link itself, detect destination entries with lstat so dangling destination links are preserved too.Regression tests cover copying a directory link over a regular file, following a file link, preserving a dangling destination link, and merging a followed directory while retaining existing content.
Validation on Windows / Node 24:
AI assistance was used to develop and validate this change.