Do added files become staged in git? -

I am reading the Pro Song book, and in the shape that confuses me is this. This indicates that the added file is not unmodified , staged it is tracked files are files that were in the previous snapshot. So I did the image that when I modified but did not modify the modified file, there would be no need to complete that change, because there is no saved version of this file in the tile cache. But I was wrong. Does this mean that the "add file" arrow should be taken from stepped state to Untrcade state?

This picture is a bit confusing, but yes. Adding an untracked file is also committed for it. The addition command is considered best to add index to the workspace, and then the change in the index is used to create the next snapshot / commit. Then git add & lt; Untracked file & gt; adds the file to the index (i.e. this step), git add & lt; Modified file & gt; adds a converted file to the index, by adding git to Deletes a deleted file (i.e. if you have removed it without using git rm ).

You can see what Git ls-files --stage . You will see that it is only for all things, such as files, their swan, and their Unix file mode (and an index number, merge trybet states, usually 0) appears for all entries, so a file is a new one Make an order by adding it to the epo, and you will see it in the list. Run this file, then run the command, and you will not see anything because you have removed the same entry from the index.

Note that the hash index has a hash index is actually just a text file (though it has been stored in binary) which are items tampered with in the object store. F Adds the file - Untracked or modified - GIT puts it in the guit / object folder, then updates the index with the entry that indicates that hash, and the path / name of that file. This is actually all index (which is usually called 'stage' or 'staged area', though these names are fading).

The next committed fact is just a text file that indicates what the index of the tree is, because where the index is basically, where do you say "this is what I want to show next. I want to. " And yes, if you add a file, replace it, you will have a version of the file in the index, and the recently updated version of the work tree, so that you have to add that, too, and git to new Will replace the version in the index with one-edited one.