admin/git
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: rephrase the purpose of the staging area

Browse Source 
Git does not really "store the contents of the next commit"
anywhere; rather, you the user use the index to prepare it.

Signed-off-by: Julia Evans <julia@jvns.ca>
[jc; made the change relative to what is already in 'next']
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Julia Evans
2025-08-29 11:55:02 +00:00
committed by Junio C Hamano
parent 929e112481
commit e5c27bd3d8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/git-add.adoc
View File

@@ -17,8 +17,8 @@ git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [-
DESCRIPTION DESCRIPTION
----------- -----------
Add contents of new or changed files to the index. The "index" (also Add contents of new or changed files to the index. The "index" (also
known as "staging area") is where Git stores the contents of the next known as the "staging area") is what you use to prepare the contents of
commit. the next commit.
When you run `git commit` without any other arguments, it will only When you run `git commit` without any other arguments, it will only
commit staged changes. For example, if you've edited `file.c` and want commit staged changes. For example, if you've edited `file.c` and want