You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/02-git-basics/sections/recording-changes.asc
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,8 @@ At this point, you should have a _bona fide_ Git repository on your local machin
4
4
Typically, you'll want to start making changes and committing snapshots of those changes into your repository each time the project reaches a state you want to record.
5
5
6
6
Remember that each file in your working directory can be in one of two states: _tracked_ or _untracked_.
7
-
Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged; in short, tracked files are files that Git knows about.
7
+
Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged.
8
+
In short, tracked files are files that Git knows about.
8
9
9
10
Untracked files are everything else – any files in your working directory that were not in your last snapshot and are not in your staging area.
10
11
When you first clone a repository, all of your files will be tracked and unmodified because Git just checked them out and you haven't edited anything.
0 commit comments