> For the complete documentation index, see [llms.txt](https://dojo.lkmx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dojo.lkmx.io/ingles/git/use-git-add.md). # Use git add **git-add** - Add file contents to the index This command updates the index using the current content found in the working tree, to prepare the content staged for the next commit. It typically adds the current content of existing paths as a whole, but with some options it can also be used to add content with only part of the changes made to the working tree files applied, or remove paths that do not exist in the working tree anymore. ## **Options** **\…​** Files to add content from. Fileglobs (e.g. `*.c`) can be given to add all matching files. Also a leading directory name (e.g. `dir` to add `dir/file1` and `dir/file2`) can be given to update the index to match the current state of the directory as a whole (e.g. specifying `dir` will record not just a file `dir/file1` modified in the working tree, a file `dir/file2` added to the working tree, but also a file `dir/file3` removed from the working tree). {% hint style="info" %} Older versions of Git used to ignore removed files; use `--no-all` option if you want to add modified or new files but ignore removed ones. {% endhint %} **-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. **--sparse** Allow updating index entries outside of the sparse-checkout cone. Normally, `git add` refuses to update index entries whose paths do not fit within the sparse-checkout cone, since those files might be removed from the working tree without warning. **-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. **-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. **-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. **-u**\ **--update** Update the index just where it already has an entry matching \. This removes as well as modifies index entries to match the working tree, but adds no new files. If no \ is given when `-u` option is used, all tracked files in the entire working tree are updated (old versions of Git used to limit the update to the current directory and its subdirectories). **-A**\ **--all**\ **--no-ignore-removal** Update the index not only where the working tree has a file matching \ but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree. If no \ is given when `-A` option is used, all files in the entire working tree are updated (old versions of Git used to limit the update to the current directory and its subdirectories). **--no-all**\ **--ignore-removal** Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This option is a no-op when no \ is used. This option is primarily to help users who are used to older versions of Git, whose "git add \…​" was a synonym for "git add --no-all \…​", i.e. ignored removed files. **-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. **--no-warn-embedded-repo** By default, `git add` will warn when adding an embedded repository to the index without using `git submodule add` to create an entry in `.gitmodules`. This option will suppress the warning (e.g., if you are manually performing operations on submodules). **--renormalize** Apply the "clean" process freshly to all tracked files to forcibly add them again to the index. This is useful after changing `core.autocrlf` configuration or the `text` attribute in order to correct files added with wrong CRLF/LF line endings. This option implies `-u`. Lone CR characters are untouched, thus while a CRLF cleans to LF, a CRCRLF sequence is only partially cleaned to CRLF. **--chmod=(+|-)x** Override the executable bit of the added files. The executable bit is only changed in the index, the files on disk are left unchanged. **--pathspec-from-file=\** Pathspec is passed in `` instead of commandline args. If `` is exactly `-` then standard input is used. Pathspec elements are separated by LF or CR/LF. Pathspec elements can be quoted as explained for the configuration variable `core.quotePath` (see [git-config\[1\]](https://git-scm.com/docs/git-config)). See also `--pathspec-file-nul` and global `--literal-pathspecs`. **--pathspec-file-nul** Only meaningful with `--pathspec-from-file`. Pathspec elements are separated with NUL character and all other characters are taken literally (including newlines and quotes). **--** This option can be used to separate command-line options from the list of files, (useful when filenames might be mistaken for command-line options). ### Common options ```xml git add  ``` Stage all changes in `` for the next commit. ```xml git add  ``` Stage all changes in `` for the next commit. ```css git add -p ``` Begin an interactive staging session that lets you choose portions of a file to add to the next commit. This will present you with a chunk of changes and prompt you for a command. Use `y` to stage the chunk, `n` to ignore the chunk, `s` to split it into smaller chunks, `e` to manually edit the chunk, and `q` to exit. ### Examples * Adds content from all `*.txt` files under `Documentation` directory and its subdirectories: ``` $ git add Documentation/\*.txt ``` Note that the asterisk `*` is quoted from the shell in this example; this lets the command include the files from subdirectories of `Documentation/` directory. * Considers adding content from all git-\*.sh scripts: ``` $ git add git-*.sh ``` Because this example lets the shell expand the asterisk (i.e. you are listing the files explicitly), it does not consider `subdir/git-foo.sh`. * When you’re starting a new project, `git add` serves the same function as `svn import`. To create an initial commit of the current directory, use the following two commands: ```undefined git add . git commit ``` Once you’ve got your project up-and-running, new files can be added by passing the path to `git add`: ```undefined git add hello.py git commit ``` The above commands can also be used to record changes to existing files. Again, Git doesn’t differentiate between staging changes in new files vs. changes in files that have already been added to the repository. ## Reference links * *