Name: Mukesh Kalikaya
Date: 25 Aug 2022
I received assistance from: No one
I assisted: No one
The git log command displays all of the commits in a repository's history.
The thing that is in common between git log and git commit is it text that was added.
Both of the commands deal with the history and changes made to the file.
When the command git status was ran, it says that file1.txt and file2.txt have to be either updated or to be included what will be committed.
Both of them are not displayed in the same section because file2.txt was newly created and it has not been added to the commit yet. While file1.txt was added to the commit after it was created. But the new changes that were made were not updated so file1.txt is in the update section and file2.txt is in the include section.
Now that both of the files have either been updated or included into the commit, it shows that file1.txt was modified and file2.txt is a new file when the command git status was ran.
When the command git status was ran, both of the files are in the same section but with different changes. file1.txt was modified and updated to commit while file2.txt was modified and then added to commit.
After the text was displayed due to the command git diff --cached, there were only 2 files that are listed as having been changed. Those are the file1.txt and file2.txt.
For file1.txt, the change/differnece listed was "This is a new line." For file2.txt, the change/difference listed was "This is a new line in a new file." The changes are being displayed in the color green.
Git told me nothing/the same thing that it told me when I ran the same command in Section 4 because no changes were made to any of the files.
I encountered quite a lot of challenges. I had no experience using git and I couldn't understand what the commands were saying and what they meant. I later got some help by searching about git and learning what the commands mean.
This experience could have been improved if I didn't have the major obstacle of not knowing git and its functions. If I knew what git was, my experience would have been a lot better and I would have experienced no issues.
I have learned that creating/using git is a good idea because if at any point you make a mistake, you don't understand what you are doing, or are just stuck, you can just go back to a point where you knew what you were doing and start from there.