-n, --dry-run
    Don’t actually add the file(s), just show if they exist and/or will be ignored.

-v, --verbose
    Be verbose.

-f, --force
    Allow adding otherwise ignored files.

-i, --interactive
    Add modified contents in the working tree interactively to the index. Optional path arguments may be
    supplied to limit operation to a subset of the working tree. See “Interactive mode” for details.

-p, --patch
    Interactively choose hunks of patch between the index and the work tree and add them to the index.
    This gives the user a chance to review the difference before adding modified contents to the index.

    This effectively runs add --interactive, but bypasses the initial command menu and directly jumps to
    the patch subcommand. See “Interactive mode” for details.

-e, --edit
    Open the diff vs. the index in an editor and let the user edit it. After the editor was closed,
    adjust the hunk headers and apply the patch to the index.

    The intent of this option is to pick and choose lines of the patch to apply, or even to modify the
    contents of lines to be staged. This can be quicker and more flexible than using the interactive hunk
    selector. However, it is easy to confuse oneself and create a patch that does not apply to the index.
    See EDITING PATCHES below.

-u, --update
    Only match <filepattern> against already tracked files in the index rather than the working tree.
    That means that it will never stage new files, but that it will stage modified new contents of
    tracked files and that it will remove files from the index if the corresponding files in the working
    tree have been removed.

    If no <filepattern> is given, default to "."; in other words, update all tracked files in the current
    directory and its subdirectories.

-A, --all
    Like -u, but match <filepattern> against files in the working tree in addition to the index. That
    means that it will find new files as well as staging modified content and removing files that are no
    longer in the working tree.

-N, --intent-to-add
    Record only the fact that the path will be added later. An entry for the path is placed in the index
    with no content. This is useful for, among other things, showing the unstaged content of such files
    with git diff and committing them with git commit -a.

--refresh
    Don’t add the file(s), but only refresh their stat() information in the index.

--ignore-errors
    If some files could not be added because of errors indexing them, do not abort the operation, but
    continue adding the others. The command shall still exit with non-zero status. The configuration
    variable add.ignoreErrors can be set to true to make this the default behaviour.

--ignore-missing
    This option can only be used together with --dry-run. By using this option the user can check if any
    of the given files would be ignored, no matter if they are already present in the work tree or not.