Skip to content
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.

Sign up for GitHub

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

Update 101-164-dataladdening.rst #966

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update 101-164-dataladdening.rst #966

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6c9457
Update 101-164-dataladdening.rst
jcolomb Jun 15, 2023
891da64
Update docs/beyond_basics/101-164-dataladdening.rst
jcolomb Jun 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/beyond_basics/101-164-dataladdening.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Consider :ref:`applying procedures <procedures>` with ``-c <procedure-name>`` to
If you want to transform a Git repository to a DataLad dataset, a :command:`datalad create -f` is the way to go, too, and completely safe.
Your Git history will stay intact and will not be tampered with.

If you want to transform a series of nested directories into nested datasets, continue with :command:`datalad create -f` commands in all further subdirectories.
If you want to transform a series of nested directories into nested datasets, you will need to use :command:`datalad create -f -d` commands giving the path of the nested directory. (If you are using the create function inside the folders, the superdataset will not treat them a subdatasets.)
jcolomb marked this conversation as resolved.
Show resolved Hide resolved

.. find-out-more:: One or many datasets?

Expand Down