-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: improve flatten: false
and rename to structured: true
#57
Conversation
Were those commits made to a protected branch? I don't think I have access to them. When opening the links on github I get the following warning: ⚠ This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. That's after doing:
|
Sorry, it didn't work.
It's my fault for getting rid of pr/47. Would you be okay with me copying the changes and recreating the commits in this PR? |
I'm fine with that 👍 |
flatten: false
and rename to structured: true
flatten: false
and rename to structured: true
flatten: false
and rename to structured: true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
@brunoimbrizi I have released this as v0.16.0! |
(Re-submitting after the git history snafu on #47)
This PR addresses #46
../
fromdir
sodest
reliably replaces the first folder in the path on.split('/')[0]
destDir
doesn't end up in the root folderdest
should be expected to containdir
whenflatten: false