.TH "datalad add" "1" "2019\-02\-08" ""datalad add 0.11.2""
.SH NAME
\fBdatalad add\fR \- add files/directories to an existing dataset.
.SH SYNOPSIS
.nh
.HP
\fBdatalad add\fR [-h] [-d\~PATH] [--to-git] [--nosave] [-m\~MESSAGE] [-F\~MESSAGE_FILE] [-r] [--recursion-limit\~LEVELS] [-S] [--git-opts\~STRING] [--annex-opts\~STRING] [--annex-add-opts\~STRING] [-J\~NJOBS] PATH [PATH ...]


.hy
.SH DESCRIPTION

Typically, files and directories to be added to a dataset would be placed
into a directory of a dataset, and subsequently this command can be used to
register this new content with the dataset. With recursion enabled,
files will be added to their respective subdatasets as well.
.PP
By default all files are added to the dataset's annex, i.e. only their
content identity and availability information is tracked with Git.
This results in lightweight datasets. If desired, the \-\-to\-git flag
can be used to tell datalad to inject files directly into Git. While
this is not recommended for binary data or large files, it can be used
for source code and meta\-data to be able to benefit from Git's track
and merge capabilities. Files checked directly into Git are always and
unconditionally available immediately after installation of a dataset.
.PP
.TP
NOTE
Power\-user info: This command uses git annex add or
git add to incorporate new dataset content.
.SH OPTIONS
.TP
PATH
path/name of the component to be added. The component must exist on the filesystem already. Constraints: value must be a string [Default: None]

.TP
\fB-h\fR, \fB--help\fR, \fB--help-np\fR
show this help message. --help-np forcefully disables the use of a pager for displaying the help message
.TP
\fB-d\fR PATH, \fB--dataset\fR PATH
specify the dataset to perform the add operation on. If no dataset is given, an attempt is made to identify the dataset based on the current working directory and/or the PATH given. Constraints: Value must be a Dataset or a valid identifier of a Dataset (e.g. a path) [Default: None]
.TP
\fB--to-git\fR
flag whether to add data directly to Git, instead of tracking data identity only. Usually this is not desired, as it inflates dataset sizes and impacts flexibility of data transport. If not specified - it will be up to git-annex to decide, possibly on .gitattributes options. [Default: None]
.TP
\fB--nosave\fR
by default all modifications to a dataset are immediately saved. Giving this option will disable this behavior. [Default: True]
.TP
\fB-m\fR MESSAGE, \fB--message\fR MESSAGE
a description of the state or the changes made to a dataset. Constraints: value must be a string [Default: None]
.TP
\fB-F\fR \fI\s-1MESSAGE_FILE\s0\fR, \fB--message-file\fR \fI\s-1MESSAGE_FILE\s0\fR
take the commit message from this file. This flag is mutually exclusive with -m. Constraints: value must be a string [Default: None]
.TP
\fB-r\fR, \fB--recursive\fR
if set, recurse into potential subdataset. [Default: False]
.TP
\fB--recursion-limit\fR LEVELS
limit recursion into subdataset to the given number of levels. Constraints: value must be convertible to type 'int' [Default: None]
.TP
\fB-S\fR, \fB--ds2super\fR, \fB--datasets-to-super\fR
given paths of dataset (toplevel) locations will cause these datasets to be added to their respective superdatasets underneath a given base DATASET (instead of all their content to themselves). If no base DATASET is provided, this flag has no effect. Regular files and directories are always added to their respective datasets, regardless of this setting. [Default: False]
.TP
\fB--git-opts\fR STRING
option string to be passed to git calls. Constraints: value must be a string [Default: None]
.TP
\fB--annex-opts\fR STRING
option string to be passed to git annex calls. Constraints: value must be a string [Default: None]
.TP
\fB--annex-add-opts\fR STRING
option string to be passed to git annex add calls. Constraints: value must be a string [Default: None]
.TP
\fB-J\fR NJOBS, \fB--jobs\fR NJOBS
how many parallel jobs (where possible) to use. Constraints: value must be convertible to type 'int', or value must be one of ('auto',) [Default: None]
.SH AUTHORS
 datalad is developed by The DataLad Team and Contributors <team@datalad.org>.