Inform git that file modifications should be added to the next commit.
Updates the index in preparation for the next commit.
If you want to start versioning a new file through git, use git add
$ touch somefile.txt
$ git add somefile.txt
$ git commit -m "Create somefile.txt"
If you make any modifications to somefile.txt, with the exception of deletion, use git add again to add the modifications to the next commit.
$ git add somefile.txt
$ git commit -m "Modified somefile.txt"
Add all modifications to all files modified since the last commit to the next commit. This includes newly created files, file modifications, and file deletions.
$ git add -A
Add all modifications to any file versioned through git that has been modified by the last commit. The difference between this and -A above is that -A will add newly created files to be committed, while this does not.
$ git add -u
You can add multiple modifications to the next commit.
$ git add f1.txt f2.txt
Wildcards can be used to conveniently add modifications of files with the same extension to the next commit.
$ git add *.py
If you're curious what modifications a git add command will add to the next commit, you can set up a "dry run" with the -n flag.
$ touch f1.txt
$ touch f2.txt
$ remove somefile.txt
$ git add -n -A
remove 'somefile.txt'
add 'f1.txt'
add 'f2.txt'
Be verbose. -n (dry-run) and -v output the same things, but -n prevents file modifications from actually being added to the next commit.
$ git add -v -A
add 'functions/git-add.md'
add 'testing.txt'
Add a file that would normally be ignored (such as by .gitignore). Suppose you currentlyare ignore all .log files, but you want to version a file called error.log.
$ git add -f error.log
Allows you to interactively add portions of modified files to the next commit. Newly created and deleted files are ignored. This is useful if you've added two functions in the same file since the last commit, but find the creation of the two function merits two commits.
$ git add -p
You will be greeted with a hunk, and options on what to do with it.
Stage this hunk [y,n,q,a,d,/,j,J,g,e,?]?
Entering '?' will provide you with a menu that defines each option:
Stage this hunk [y,n,q,a,d,/,j,J,g,e,?]? ?
y - stage this hunk
n - do not stage this hunk
q - quit; do not stage this hunk nor any of the remaining ones
a - stage this hunk and all later hunks in the file
d - do not stage this hunk nor any of the later hunks in the file
g - select a hunk to go to
/ - search for a hunk matching the given regex
j - leave this hunk undecided, see next undecided hunk
J - leave this hunk undecided, see next hunk
k - leave this hunk undecided, see previous undecided hunk
K - leave this hunk undecided, see previous hunk
s - split the current hunk into smaller hunks
e - manually edit the current hunk
? - print help
View the official man page
$ man git-add